1257025 - Add ability to retrigger jobs/highlight suites that include a specific test

Status: RESOLVED DUPLICATE of bug 1149670

(Testing :: General, defect)

Description

[Jared Wein [:jaws] (please needinfo? me)]

<jaws> looking at https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1064580&startday=2016-03-07&endday=2016-03-13&tree=all, why do some runs have the test running in e10s-bc3 then others have it running in e10s-bc1 on the same platform and same debug/opt output?
<jaws> see the outputs for linux for example
<jaws> philor: do you know? ^
<philor> jaws: browser-chrome and devtools are run --chunk-by-dir, which attempts to balance out the runtime between chunks while still keeping tests in the same directory run together, so any patch which adds, removes, enables or disables a test can move every single test to a new chunk
<jaws> philor: thanks. i suppose it would be nice to be able to retrigger a job based on a test name
<jaws> right now i retrigger a bunch of jobs on an intermittent failure and then find out later that it was the wrong suite and i wasted compute time as well as my own time
PM <jaws> if i could say "run the suite that includes test XYZ 5 times" it would be perfect

Comment 1

[Ed Morley [:emorley]]

I believe this is possible already, via bug 1149670 (which is also usable via trychooser I believe - bug 1177653).

There are a few quirks (eg bug 1255674), but I think most of these will need fixing in mozci/trychooser/try extender rather than Treeherder (since Treeherder doesn't do any scheduling, it only pokes various APIs to request builds/cancellations etc).

I'm going to mark this as a dupe of bug 1149670, however if there are Treeherder UI parts that could be improved, feel free to file bugs about those specifically (though Treeherder itself doesn't really know what tests ran in each job, so options are limited on that front).

Thank you for filing :-)