On 2016-06-24 22:08:40 +0000 (+0000), Jeremy Stanley wrote:
[...]
> the gate-horizon-npm-run-test job uses that same configuration
> (just passing a different {command}) and we're still seeing
> failures registered for it even now.
[...]Just following up since I got a few more minutes to poke at this after discussing in IRC: I have confirmed the stats we have in graphite seem to match what's recorded by logstash, and dug up three example failure logs from today. http://logs.openstack.org/00/334300/1/check/gate-horizon-npm-run-test/469ff89/console.html http://logs.openstack.org/03/320203/9/check/gate-horizon-npm-run-test/e71f803/console.html http://logs.openstack.org/28/333628/5/check/gate-horizon-npm-run-test/5ae2085/console.html However, there's (thankfully) a consistent explanation. Take a look at the timestamp gaps between the penultimate and ultimate lines of each log... timeouts! So I agree the issue seems to be lack of errexit in the npm-run builder. The old failures observed for gate-horizon-npm-run-lint are probably similarly explained as timeout issues we've just been lucky enough not to hit in the past week or so. Unfortunately those failures fall just outside our elasticsearch retention window so confirming that would be a very time-intensive exercise at this point. -- Jeremy Stanley __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
