There's sort of a way to do this with try syntax. I say sort of because it doesn't support all suites and there seems to be a few bugs with it. But you can try:
./mach try -b o -p linux64 -u none path/to/dir/or/test This should only run the directory or test you specified (it'll always show up as chunk 1). I have vague plans to implement this a bit more robustly for try_task_config.json based scheduling, but no time frame on when that work might happen yet. -Andrew On Thu, Sep 14, 2017 at 11:48 AM Marco Bonardo <[email protected]> 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? > > -- > You received this message because you are subscribed to the Google Groups > "firefox-ci" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/a/mozilla.com/d/msgid/firefox-ci/CAPDqYT151ETZSGM83Wo_jdpSj1bHhs57eTpah4bE5PE2BM9ckQ%40mail.gmail.com > . > _______________________________________________ dev-platform mailing list [email protected] https://lists.mozilla.org/listinfo/dev-platform
