James E. Blair abf7d0e35a Suppress some bugs from the e-r graph page ... Depending on exactly at what point a build in Jenkins is aborted, sometimes it can end up with a result of FAILURE. Since logstash gets its data from Jenkins rather than Zuul, it doesn't know the build has aborted. Since ER gets its data from logstash, it also doesn't know that some failures are actually just aborted builds. We want to know that we should ignore these failures for classification rate purposes, but we should not display them on the graph page as they are not actionable bugs. Change-Id: If381e36144ffc03c0e36d3eb74ad7f24db245aa6		2014-02-10 16:39:44 -08:00
..
cmd	Suppress some bugs from the e-r graph page	2014-02-10 16:39:44 -08:00
tests	Map failed jobs to bugs in gerrit comment	2014-02-06 15:58:27 -08:00
__init__.py	Further shuffling to get this to fit the standard code layout	2013-09-25 18:20:51 -07:00
bot.py	Convert failed_job into an object	2014-02-06 15:56:27 -08:00
elasticRecheck.py	Merge "ensure all the required files are there"	2014-02-08 01:09:44 +00:00
loader.py	Stop logging skipped bugs	2014-01-23 16:30:10 -08:00
query_builder.py	Add option to elastic-recheck-graph to pick a single queue	2014-01-30 13:40:52 -08:00
results.py	Remove remaining cases of '@message'	2014-01-19 19:10:33 -08:00