opendev/elastic-recheck
Code Issues Proposed changes
d08db6f789
elastic-recheck/elastic_recheck/tests/unit
History
Joe Gordon 14bfee5646 Don't include recheck instructions when unclassified failures 
If there is an unclassified failure in the check queue, we want to make
it clear to the user so they will investigate the error as its most
likely a valid failure. Also don't include recheck instructions when
unclassified failure as they shouldn't be running a recheck if there is
an unclassified failure.

With us now classifying many failures from non-voting jobs, it is common
to see classified failures and no mention of the job that legitimately
failed.

Partial revert of I52044afb4f3a1bf3f22ba4c0e8d38d76271ffc00

Change-Id: I6b471b9ab9c7f36eeed93993ea086bbc9daa56b0
2014-04-01 21:21:44 -07:00
..
gerrit only care about unclassifieds in gate queue 2014-03-12 17:07:43 -04:00
jenkins parse the failed jobs in stream 2014-01-13 14:41:55 -05:00
queries move queries.yaml into a queries subdir 2013-12-02 11:43:00 -05:00
samples refactor templates into query_builder 2013-10-21 13:46:57 -04:00
__init__.py move queries.yaml into a queries subdir 2013-12-02 11:43:00 -05:00
fake_gerrit.py moving readiness checks into stream 2014-01-13 20:00:23 -05:00
test_bot.py Make IRC bot list which failures were seen in which job. 2014-03-13 10:25:32 -07:00
test_elastic_recheck.py move queries.yaml into a queries subdir 2013-12-02 11:43:00 -05:00
test_load_queries.py remove old queries 2014-02-25 08:35:51 -05:00
test_results.py move the graph generating code over to facets 2013-12-06 17:40:31 -05:00
test_stream.py Don't include recheck instructions when unclassified failures 2014-04-01 21:21:44 -07:00