<div dir="ltr">JFYI, CR [1] which fixes the corresponding bug [2] was merged on Jun 28, so it may make sense to recheck you perfectly looking commit if it has been staying in Gerrit for a while.<div><br></div><div>[1] <a href="https://review.openstack.org/#/c/334582/">https://review.openstack.org/#/c/334582/</a></div><div>[2] <a href="https://bugs.launchpad.net/horizon/+bug/1595938">https://bugs.launchpad.net/horizon/+bug/1595938</a></div></div><br><div class="gmail_quote"><div dir="ltr">On Mon, Jun 27, 2016 at 10:42 PM Jeremy Stanley <<a href="mailto:fungi@yuggoth.org">fungi@yuggoth.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 2016-06-24 22:08:40 +0000 (+0000), Jeremy Stanley wrote:<br>
[...]<br>
> the gate-horizon-npm-run-test job uses that same configuration<br>
> (just passing a different {command}) and we're still seeing<br>
> failures registered for it even now.<br>
[...]<br>
<br>
Just following up since I got a few more minutes to poke at this<br>
after discussing in IRC: I have confirmed the stats we have in<br>
graphite seem to match what's recorded by logstash, and dug up<br>
three example failure logs from today.<br>
<br>
<a href="http://logs.openstack.org/00/334300/1/check/gate-horizon-npm-run-test/469ff89/console.html" rel="noreferrer" target="_blank">http://logs.openstack.org/00/334300/1/check/gate-horizon-npm-run-test/469ff89/console.html</a><br>
<br>
<a href="http://logs.openstack.org/03/320203/9/check/gate-horizon-npm-run-test/e71f803/console.html" rel="noreferrer" target="_blank">http://logs.openstack.org/03/320203/9/check/gate-horizon-npm-run-test/e71f803/console.html</a><br>
<br>
<a href="http://logs.openstack.org/28/333628/5/check/gate-horizon-npm-run-test/5ae2085/console.html" rel="noreferrer" target="_blank">http://logs.openstack.org/28/333628/5/check/gate-horizon-npm-run-test/5ae2085/console.html</a><br>
<br>
However, there's (thankfully) a consistent explanation. Take a look<br>
at the timestamp gaps between the penultimate and ultimate lines of<br>
each log... timeouts! So I agree the issue seems to be lack of<br>
errexit in the npm-run builder. The old failures observed for<br>
gate-horizon-npm-run-lint are probably similarly explained as<br>
timeout issues we've just been lucky enough not to hit in the past<br>
week or so. Unfortunately those failures fall just outside our<br>
elasticsearch retention window so confirming that would be a very<br>
time-intensive exercise at this point.<br>
--<br>
Jeremy Stanley<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>
</blockquote></div>