<div dir="ltr">Tim,<div><br></div><div>Previous failure on gate is fixed with this patch <a href="https://review.openstack.org/#/c/247314/">https://review.openstack.org/#/c/247314/</a></div><div>Now congress tempest tests are running, so our tempest plugin worked :)</div><div><a href="http://logs.openstack.org/10/237510/5/check/gate-congress-dsvm-api/0bdbb53/console.html">http://logs.openstack.org/10/237510/5/check/gate-congress-dsvm-api/0bdbb53/console.html</a><br></div><div><br></div><div>Current gate failures report a different issue which should be solved by this patch</div><div><a href="https://review.openstack.org/#/c/247375/2">https://review.openstack.org/#/c/247375/2</a><br></div><div><br></div><div>Best Regards,<br></div><div class="gmail_extra"><div><div class="gmail_signature"><div dir="ltr"><div dir="ltr"><div>Anusha</div></div></div></div></div>
<br><div class="gmail_quote">On 23 November 2015 at 22:00, Tim Hinrichs <span dir="ltr"><<a href="mailto:tim@styra.com" target="_blank">tim@styra.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr">It looks like our tempest tests aren't running in the gate.  Here's a recent patch that just merged this morning.<div><br><div><div><a href="https://review.openstack.org/#/c/242305/" target="_blank">https://review.openstack.org/#/c/242305/</a><br></div></div><div><br></div><div>If you go to the testr results, you'll see a list of all the tests that were run. </div><div> </div><div><a href="http://logs.openstack.org/05/242305/5/gate/gate-congress-dsvm-api/979bc9d/testr_results.html.gz" target="_blank">http://logs.openstack.org/05/242305/5/gate/gate-congress-dsvm-api/979bc9d/testr_results.html.gz</a><br></div><div><br></div><div>Two things: (i) there are many tests here that are not Congress-specific and (ii) I don't see the Congress tests running at all.  During manual testing both these issues were handled by the following lines in our gate job config.</div><div><br></div><div><a href="https://github.com/openstack-infra/project-config/blob/master/jenkins/jobs/congress.yaml#L33-L34" target="_blank">https://github.com/openstack-infra/project-config/blob/master/jenkins/jobs/congress.yaml#L33-L34</a><br></div><div><br></div><div>The good news, at least, is that congress is getting properly spun up.</div><div><br></div><div><a href="http://logs.openstack.org/05/242305/5/gate/gate-congress-dsvm-api/979bc9d/logs/screen-congress.txt.gz" target="_blank">http://logs.openstack.org/05/242305/5/gate/gate-congress-dsvm-api/979bc9d/logs/screen-congress.txt.gz</a><br></div><div><br></div><div>Would someone want to volunteer to dig into this?</div><span class=""><font color="#888888"><div><br></div><div>Tim</div><div><br></div></font></span></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>