You can try ActiveData, which stores all test results from the past few weeks. Here is an example query that shows the chunk number for each run/build combo in the past day. ActiveData is sometimes more than a day behind
https://activedata.allizom.org/tools/query.html#query_id=4HHuBgDu { "from":"unittest", "select":[ {"aggregate":"count"}, {"value":"action.start_time","aggregate":"max"} ], "groupby":[ "run.suite", "run.chunk", "result.test", "build.platform", "build.type", "run.type" ], "where":{"and":[ {"eq":{"build.branch":"mozilla-inbound"}}, {"prefix":{"run.suite":"moch"}}, {"gt":{"action.start_time":{"date":"today-day"}}}, {"regex":{"result.test":".*browser_623779.js.*"}} ]}, "limit":1000 } On 2017-09-14 11:49, Michael de Boer wrote: >> On 14 Sep 2017, at 17:48, Marco Bonardo <mbona...@mozilla.com> wrote: >> >> When I need to retrigger a mochitest-browser test multiple times (to >> investigate an intermittent), often I end up running all the >> mochitest-browser tests, looking at every log until I find the chunk >> where the test is, and retrigger just that chunk. The chunk number >> changes based on the platform and debug/opt, so it's painful. >> Is there a way to trigger only the chunk that will contain a given >> test, so I can save running all of the other chunks? > This! This! This! I’d love to be able to do this - would making testing > possible test failure fixes sooo much easier. > > Cheers, > > Mike. > _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
