<p dir="ltr">Quick update on this, the change is now merged, so we now have a smaller number of scenario tests running serially after the api test run.</p>
<p dir="ltr">We'll monitor gate stability for the next week or so and decide whether further actions are required.</p>
<p dir="ltr">Please keep categorizing failures via elastic recheck as usual.</p>
<p dir="ltr">thank you</p>
<p dir="ltr">andrea</p>
<br><div class="gmail_quote"><div dir="ltr">On Fri, 3 Mar 2017, 8:02 a.m. Ghanshyam Mann, <<a href="mailto:ghanshyammann@gmail.com">ghanshyammann@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr" class="gmail_msg"><div class="gmail_default gmail_msg" style="font-family:arial,helvetica,sans-serif;color:rgb(0,0,0)">Thanks. +1. i added my list in ethercalc.</div><div class="gmail_default gmail_msg" style="font-family:arial,helvetica,sans-serif;color:rgb(0,0,0)"><br class="gmail_msg"></div><div class="gmail_default gmail_msg" style="font-family:arial,helvetica,sans-serif;color:rgb(0,0,0)">Left put scenario tests can be run on periodic and experimental job. IMO on both ( periodic and experimental) to monitor their status periodically as well as on particular patch if we need to. </div><div class="gmail_extra gmail_msg"><br clear="all" class="gmail_msg"><div class="gmail_msg"><div class="m_7817127192274301852gmail_signature gmail_msg" data-smartmail="gmail_signature"><div dir="ltr" class="gmail_msg"><div class="gmail_msg">-gmann</div></div></div></div>
<br class="gmail_msg"><div class="gmail_quote gmail_msg"></div></div></div><div dir="ltr" class="gmail_msg"><div class="gmail_extra gmail_msg"><div class="gmail_quote gmail_msg">On Fri, Mar 3, 2017 at 4:28 PM, Andrea Frittoli <span dir="ltr" class="gmail_msg"><<a href="mailto:andrea.frittoli@gmail.com" class="gmail_msg" target="_blank">andrea.frittoli@gmail.com</a>></span> wrote:<br class="gmail_msg"></div></div></div><div dir="ltr" class="gmail_msg"><div class="gmail_extra gmail_msg"><div class="gmail_quote gmail_msg"><blockquote class="gmail_quote gmail_msg" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr" class="gmail_msg">Hello folks,<div class="gmail_msg"><br class="gmail_msg"></div><div class="gmail_msg">we discussed a lot since the PTG about issues with gate stability; we need a stable and reliable gate to ensure smooth progress in Pike.</div><div class="gmail_msg"><br class="gmail_msg"></div><div class="gmail_msg">One of the issues that stands out is that most of the times during test runs our test VMs are under heavy load.</div><div class="gmail_msg">This can be the common cause behind several failures we've seen in the gate, so we agreed during the QA meeting yesterday [0] that we're going to try reducing the load and see whether that improves stability.<br class="gmail_msg"></div><div class="gmail_msg"><br class="gmail_msg"></div><div class="gmail_msg">Next steps are:<br class="gmail_msg"></div><div class="gmail_msg">- select a subset of scenario tests to be executed in the gate, based on [1], and run them serially only </div><div class="gmail_msg">- the patch for this is [2] and we will approve this by the end of the day</div><div class="gmail_msg">- we will monitor stability for a week - if needed we may reduce concurrency a bit on API tests as well, and identify "heavy" tests candidate for removal / refactor</div><div class="gmail_msg">- the QA team won't approve any new test (scenario or heavy resource consuming api) until gate stability is ensured </div><div class="gmail_msg"><br class="gmail_msg"></div><div class="gmail_msg">Thanks for your patience and collaboration!</div><div class="gmail_msg"><br class="gmail_msg"></div><div class="gmail_msg">Andrea</div><div class="gmail_msg"><br class="gmail_msg"></div><div class="gmail_msg">---</div><div class="gmail_msg">irc: andreaf</div><div class="gmail_msg"><br class="gmail_msg"></div><div class="gmail_msg">[0] <a href="http://eavesdrop.openstack.org/meetings/qa/2017/qa.2017-03-02-17.00.txt" class="gmail_msg" target="_blank">http://eavesdrop.openstack.org/meetings/qa/2017/qa.2017-03-02-17.00.txt</a></div><div class="gmail_msg">[1] <a href="https://ethercalc.openstack.org/nu56u2wrfb2b" class="gmail_msg" target="_blank">https://ethercalc.openstack.org/nu56u2wrfb2b</a></div><div class="gmail_msg">[2] <span style="white-space:pre-wrap" class="gmail_msg"><a href="https://review.openstack.org/#/c/439698/" class="gmail_msg" target="_blank">https://review.openstack.org/#/c/439698/</a> </span></div></div>
<br class="gmail_msg"></blockquote></div></div></div><div dir="ltr" class="gmail_msg"><div class="gmail_extra gmail_msg"><div class="gmail_quote gmail_msg"><blockquote class="gmail_quote gmail_msg" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">__________________________________________________________________________<br class="gmail_msg">
OpenStack Development Mailing List (not for usage questions)<br class="gmail_msg">
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" class="gmail_msg" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br class="gmail_msg">
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" class="gmail_msg" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class="gmail_msg">
<br class="gmail_msg"></blockquote></div><br class="gmail_msg"></div></div>
__________________________________________________________________________<br class="gmail_msg">
OpenStack Development Mailing List (not for usage questions)<br class="gmail_msg">
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" class="gmail_msg" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br class="gmail_msg">
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" class="gmail_msg" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class="gmail_msg">
</blockquote></div>