(In reply to Mark Banner (:standard8) from comment #4) > At one time you could pass `--tag` to [try syntax](https://wiki.mozilla.org/ReleaseEngineering/TryChooser#What_if_I_want_to_run_a_sub-set_of_tests_for_a_job.3F), however that [appears broken now](https://bugzilla.mozilla.org/show_bug.cgi?id=1336606). Yes, we should get this working again. In the meantime... I just recently landed in-tree presets: https://firefox-source-docs.mozilla.org/tools/try/presets.html#editing-and-sharing-presets This means you can add a preset to [tools/tryselect/try_presets.yml](https://searchfox.org/mozilla-central/source/tools/tryselect/try_presets.yml) and it will be available to everyone with: $ ./mach try --preset <name> There are still a couple of follow-up series in the process of landing to make these work a bit better, so I haven't advertised them yet, but feel free to go ahead and add one. Note: I strongly recommend creating presets with |mach try fuzzy|, even if you use |mach try syntax| locally. Not only because I prefer fuzzy, but because: A) It is well structured B) It is more powerful C) People will be able to post-filter the preset selection (once bug 1531360 lands) If you aren't familiar with fuzzy, please ping me and I can help you craft a preset.
Bug 1532809 Comment 5 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to Mark Banner (:standard8) from comment #4) > At one time you could pass `--tag` to [try syntax](https://wiki.mozilla.org/ReleaseEngineering/TryChooser#What_if_I_want_to_run_a_sub-set_of_tests_for_a_job.3F), however that [appears broken now](https://bugzilla.mozilla.org/show_bug.cgi?id=1336606). Yes, we should get this working again. In the meantime... I just recently landed in-tree presets: https://firefox-source-docs.mozilla.org/tools/try/presets.html#editing-and-sharing-presets This means you can add a preset to [tools/tryselect/try_presets.yml](https://searchfox.org/mozilla-central/source/tools/tryselect/try_presets.yml) and it will be available to everyone with: $ ./mach try --preset <name> There are still a couple of follow-up series in the process of landing to make these work a bit better, so I haven't advertised them yet, but feel free to go ahead and add one. Note: I strongly recommend creating presets with |mach try fuzzy|, even if you use |mach try syntax| locally. Not only because I prefer fuzzy, but because: A) It is well structured B) It is more powerful C) People will be able to post-filter the preset selection (once bug 1531360 lands) D) You can select tasks much more granularly If you aren't familiar with fuzzy, please ping me and I can help you craft a preset.