1161326 - Add intermittent bugs to ActiveData

Status: RESOLVED WORKSFORME

(Testing Graveyard :: ActiveData, defect)

Description

[Kyle Lahnakoski [:ekyle]]

Joel's list of intermittents:

    https://docs.google.com/spreadsheets/d/1QeZuZ4hX-LUTXhB93ogWFZO_idX7gNnyO0RF_Z6PZss/edit#gid=47775445

Link to example intermittent: 

    https://bugzilla.mozilla.org/show_bug.cgi?id=1137412

Some code that tries to match the star to the bug number: 

    https://github.com/mozilla/treeherder/blob/4824072e39c78fd96ea4d668f536f2927d7473e0/treeherder/log_parser/utils.py#L123

Link to ModevMetrics query tool:

    http://people.mozilla.org/~klahnakoski/modevmetrics/Util-QueryTool.html

Bugzilla ES query for all intermittents:
> {
>     "from":"public_bugs",
>     "select":["bug_id","short_desc"],
>     "esfilter":{"and":[
>         {"term":{"keyword":"intermittent-failure"}},
>         {"range":{"expires_on":{"gt":1430781113000}}}
>     ]}
> }

Comment 1

[Kyle Lahnakoski [:ekyle]]

JSON endpoint for a revision:
> https://treeherder.mozilla.org/#/jobs?repo=mozilla-inbound&revision=ef2faa9a0845

JSON endpoint for a result set
> https://treeherder.mozilla.org/api/project/mozilla-inbound/jobs/?result_set_id=15029

Comment 2

[Kyle Lahnakoski [:ekyle]]

Marking up AD test results with BZ `intermittent-failures` will require a daemon to do so.  Alternately, it could be done by the intermittent summarization tool at request time (after all, it has access to the BZ ES cluster to do this).

Which is better?

Comment 3

[Joel Maher ( :jmaher ) (UTC -8)]

either is better- probably the daemon approach will be faster, but I see no harm in doing it in the summarization end.

Comment 4

[Kyle Lahnakoski [:ekyle]]

I forget the exact purpose of this bug.  We have NeglectedOranges; which seems to satisfy most of the need here.  Re-open this bug if I am wrong.