<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Aug 28, 2015 at 1:50 PM, Salvatore Orlando <span dir="ltr"><<a href="mailto:salv.orlando@gmail.com" target="_blank">salv.orlando@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote"><div><div class="h5">On 28 August 2015 at 16:57, Sean Dague <span dir="ltr"><<a href="mailto:sean@dague.net" target="_blank">sean@dague.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span>On 08/28/2015 11:20 AM, Assaf Muller wrote:<br>
> To recap, we had three issues impacting the gate queue:<br>
><br>
> 1) The neutron functional job has had a high failure rate for a while<br>
> now. Since it's impacting the gate,<br>
> I've removed it from the gate queue but kept it in the Neutron check queue:<br>
> <a href="https://review.openstack.org/#/c/218302/" rel="noreferrer" target="_blank">https://review.openstack.org/#/c/218302/</a><br>
><br>
> If you'd like to help, the the list of bugs impacting the Neutron<br>
> functional job is linked in that patch.<br>
><br>
> 2) A new Tempest scenario test was added that caused the DVR job failure<br>
> rate to sky rocket to over 50%.<br>
> It actually highlighted a legit bug with DVR and legacy routers. Kevin<br>
> proposed a patch that skips that test<br>
> entirely until we can resolve the bug in Neutron:<br>
> <a href="https://review.openstack.org/#/c/218242/" rel="noreferrer" target="_blank">https://review.openstack.org/#/c/218242/</a> (Currently it tries to skip the<br>
> test conditionally, the next PS will skip the test entirely).<br>
><br>
> 3) The Neutron py34 job has been made unstable due to a recent change<br>
> (By me, yay) that made the tests<br>
> run with multiple workers. This highlighted an issue with the Neutron<br>
> unit testing infrastructure, which is fixed here:<br>
> <a href="https://review.openstack.org/#/c/217379/" rel="noreferrer" target="_blank">https://review.openstack.org/#/c/217379/</a><br>
><br>
> With all three patches merged we should be good to go.<br>
<br>
</span>Well, with all 3 of these we should be much better for sure. There are<br>
probably additional issues causing intermittent failures which should be<br>
looked at. These 3 are definitely masking anything else.<br></blockquote><div><br></div></div></div><div>Sadly, since the issues are independent, it is very likely for one of the patch to fail jenkins tests for one of the other two issues.</div><div>If the situation persists is it crazy to conside switching neutron-py34 and neutron-functional to non-voting until these patches merge.</div><div>Neutron cores might abstain from approving patches (unless trivial or documentation) while these jobs are non-voting.</div></div></div></div></blockquote><div><br></div><div>We have two of the three merged. The Neutron functional tests are no longer part of the gate queue, only the check queue,</div><div>and the Tempest router_reschedule test will no longer fail as part of the DVR job. This means that the py34 patch now has</div><div>a better chance of going in.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><span class=""><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
<a href="https://etherpad.openstack.org/p/gate-fire-2015-08-28" rel="noreferrer" target="_blank">https://etherpad.openstack.org/p/gate-fire-2015-08-28</a> is a set of<br>
patches to promote for things causing races in the gate (we've got a<br>
cinder one was well). If other issues are known with fixes posted,<br>
please feel free to add them with comments.<br></blockquote><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><div><br>
-Sean<br>
<br>
--<br>
Sean Dague<br>
<a href="http://dague.net" rel="noreferrer" target="_blank">http://dague.net</a><br>
<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>
</div></div></blockquote></span></div><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>