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
..
cmd	Fix elasticsearch URL for gate queue	2014-03-20 10:30:25 -07:00
tests	Don't include recheck instructions when unclassified failures	2014-04-01 21:21:44 -07:00
__init__.py	Further shuffling to get this to fit the standard code layout	2013-09-25 18:20:51 -07:00
bot.py	Take advantage of the new build_short_uuid field.	2014-03-26 12:14:32 -07:00
elasticRecheck.py	Don't include recheck instructions when unclassified failures	2014-04-01 21:21:44 -07:00
loader.py	Revert "move to static LOG"	2014-03-06 11:12:43 -08:00
query_builder.py	Take advantage of the new build_short_uuid field.	2014-03-26 12:14:32 -07:00
results.py	Improved timestamp parsing	2014-02-20 20:39:41 -05:00