<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On 2 February 2016 at 19:03, Matthew Treinish <span dir="ltr"><<a href="mailto:mtreinish@kortar.org" target="_blank">mtreinish@kortar.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Tue, Feb 02, 2016 at 05:09:47PM -0800, Armando M. wrote:<br>
> Folks,<br>
><br>
> We have some IPv6 related bugs [1,2,3] that have been lingering for some<br>
> time now. They have been hurting the gate (e.g. [4] the most recent<br>
> offending failure) and since it looks like they have been without owners<br>
> nor a plan of action for some time, I made the hard decision of skipping<br>
> them [5] ahead of the busy times ahead.<br>
<br>
</span>So TBH I don't think the failure rate for these tests are really at a point<br>
necessitating a skip:<br>
<br>
<a href="http://status.openstack.org/openstack-health/#/test/tempest.scenario.test_network_v6.TestGettingAddress.test_multi_prefix_slaac" rel="noreferrer" target="_blank">http://status.openstack.org/openstack-health/#/test/tempest.scenario.test_network_v6.TestGettingAddress.test_multi_prefix_slaac</a><br>
<a href="http://status.openstack.org/openstack-health/#/test/tempest.scenario.test_network_v6.TestGettingAddress.test_dualnet_dhcp6_stateless_from_os" rel="noreferrer" target="_blank">http://status.openstack.org/openstack-health/#/test/tempest.scenario.test_network_v6.TestGettingAddress.test_dualnet_dhcp6_stateless_from_os</a><br>
<a href="http://status.openstack.org/openstack-health/#/test/tempest.scenario.test_network_v6.TestGettingAddress.test_dhcp6_stateless_from_os" rel="noreferrer" target="_blank">http://status.openstack.org/openstack-health/#/test/tempest.scenario.test_network_v6.TestGettingAddress.test_dhcp6_stateless_from_os</a><br>
<br>
(also just a cool side-note, you can see the very obvious performance regression<br>
caused by the keystonemiddleware release and when we excluded that version in<br>
requirements)<br>
<br>
Well, test_dualnet_dhcp6_stateless_from_os is kinda there with a ~10% failure<br>
rate, but the other 2 really aren't. I normally would be -1 on the skip patch<br>
because of that. We try to save the skips for cases where the bugs are really<br>
severe and preventing productivity at a large scale.<br></blockquote><div><br></div><div>I am being overly aggressive here, just because I am conscious of the time of the year :)</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
But, in this case these ipv6 tests are kinda of out of place in tempest. Having<br>
all the permutations of possible ip allocation configurations always seemed a<br>
bit too heavy handed. These tests are also consistently in the top 10 slowest<br>
for a run. We really should have trimmed down this set a while ago so we're only<br>
have a single case in tempest. Neutron should own the other possible<br>
configurations as an in-tree test.<br></blockquote><div><br></div><div>+1</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Brian Haley has a patch up from Dec. that was trying to clean it up:<br>
<br>
<a href="https://review.openstack.org/#/c/239868/" rel="noreferrer" target="_blank">https://review.openstack.org/#/c/239868/</a><br>
<br>
We probably should revisit that soon, since quite clearly no one is looking at<br>
these right now.<br>
<br></blockquote><div><br></div><div>I thought that had merged already...my memory doesn't serve me as it used to anymore :(</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
-Matt Treinish<br>
<div class="HOEnZb"><div class="h5"><br>
<br>
><br>
> Now one might argue that skipping them is counterproductive because it may<br>
> allow other regressions to sneak in, but I am hoping that this<br>
> controversial action will indeed smoke out the right folks.<br>
><br>
> Comments welcome.<br>
><br>
> Regards,<br>
> Armando<br>
><br>
> [1] <a href="https://bugs.launchpad.net/neutron/+bug/1477192" rel="noreferrer" target="_blank">https://bugs.launchpad.net/neutron/+bug/1477192</a><br>
> [2] <a href="https://bugs.launchpad.net/neutron/+bug/1509004" rel="noreferrer" target="_blank">https://bugs.launchpad.net/neutron/+bug/1509004</a><br>
> [3] <a href="https://bugs.launchpad.net/openstack-gate/+bug/1540983" rel="noreferrer" target="_blank">https://bugs.launchpad.net/openstack-gate/+bug/1540983</a><br>
> [4]<br>
> <a href="http://logs.openstack.org/37/264937/5/gate/gate-tempest-dsvm-neutron-full/afeaabd//logs/testr_results.html.gz" rel="noreferrer" target="_blank">http://logs.openstack.org/37/264937/5/gate/gate-tempest-dsvm-neutron-full/afeaabd//logs/testr_results.html.gz</a><br>
> [5] <a href="https://review.openstack.org/#/c/275457/" rel="noreferrer" target="_blank">https://review.openstack.org/#/c/275457/</a><br>
<br>
</div></div><br>__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div></div>