4 Commits

Author	SHA1	Message	Date
Sorin Sbarnea	c2c3f3a683	Identify *POST* timeout failures individually ... Ability to identify only POST timeout failuse is critical because in most cases this is an infra/ci related issue which has nothing to do with the change itself. As opposed to normal timeouts, this needs more attention from CI/infra because almost for sure it means missing or partial logs. Also changes original query so they would not overlap. Change-Id: I3b112d4784c0f7dd57a26d08335c3cbe374eb90e LogStash: http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%20%5C%22POST-RUN%20END%20RESULT_TIMED_OUT%5C%22%20AND%20tags%3A%20%5C%22console%5C%22%20AND%20voting%3A1 Related-Bug: 1807940	2018-12-27 16:00:19 +00:00
Sorin Sbarnea	673c7b6ec6	Improve generic zuul timeouts identification: RESULT_TIMED_OUT ... Looks for RUN END RESULT_TIMED_OUT and link them to tracer bug. Change-Id: I95953b124c3c491820a318a5bfd75d39de14e088 Story: https://tree.taiga.io/project/tripleo-ci-board/issue/308 Related-Bug: 1686542	2018-11-19 19:47:41 +00:00
Bogdan Dobrelya	3bd6a4f8fa	Fix Generic job timeout bug match ... Add error code 143, which shows more than 95% FAILURE rates and is the most common for tripleo-ci jobs timing out. Change-Id: I98a0e77011ab259095d3e5f269ceeea16ecf8002 Signed-off-by: Bogdan Dobrelya <bdobreli@redhat.com>	2017-08-10 12:21:31 +02:00
Clark Boylan	797f6ce277	Track job timeouts in e-r ... So that timed out jobs are classified as timing out and not noise in the uncategorized list lets track these generically. We can also have specific timeout bugs tracked in addition to this one (and at least one is the the neutron multinode linuxbridge test). Change-Id: I18b6f312ea3e81755c23285287c4192d8dd87a14 Related-bug: 1686542	2017-04-26 15:55:02 -07:00