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
..
2018-04-09 10:55:53 +00:00
2017-08-04 08:52:30 -07:00
2014-12-09 17:21:42 -05:00
2015-01-23 09:44:27 -08:00
2016-02-01 07:55:30 -08:00
2016-02-03 07:19:47 -05:00
2016-12-19 12:30:21 +00:00
2017-06-13 14:38:28 +01:00
2017-05-02 15:42:19 -04:00
2017-08-04 09:16:15 -07:00
2017-08-09 22:01:00 -04:00
2017-12-19 13:17:49 -07:00
2018-12-12 11:38:16 -05:00
2018-07-10 12:38:07 -04:00
2018-04-13 16:44:22 +00:00
2018-10-08 18:10:38 -04:00
2018-07-25 10:01:20 -04:00
2018-08-22 12:29:40 -04:00
2018-08-31 10:44:35 -04:00
2018-10-04 10:32:55 -07:00
2018-11-02 10:27:04 -04:00
2018-11-26 20:34:24 +00:00
2018-12-12 19:19:04 +00:00