Intent to change default try selector from `syntax` to `auto` (ACTION NEEDED for try syntax users)

71 views
Skip to first unread message

Andrew Halberstadt

unread,
Jul 6, 2020, 12:33:55 PM7/6/20
to dev-platform, Firefox Dev
Hello everyone,

On Friday July 10th we intend to change the default try selector from
"syntax" to "auto". This means running `mach try` (with no subcommand) will
invoke `mach try auto` rather than `mach try syntax`. If you don't use try
syntax, this change will not impact your workflow.

If you do use try syntax (e.g, `mach try -b do ..`), then you have two
options:

1. Type `mach try syntax -b do ..` instead
2. Specify a custom default by editing `~/.mozbuild/machrc` (create it
first if it doesn't exist) and adding:
```
[try]
default = syntax
```

Try syntax users can make this change to their `machrc` right now for a
seamless transition when the change hits central. Please let me know if you
have questions or concerns.

Cheers,
Andrew

p.s For those who may be unaware, |mach try syntax| uses an outdated (and
poorly supported) method for selecting tasks on try and requires some
arcane knowledge. Whereas |mach try auto| is a new selector that aims to
make the decision on your behalf, requiring no special CI-related
knowledge, thus being a better default.

Tom Ritter

unread,
Jul 6, 2020, 12:50:45 PM7/6/20
to Andrew Halberstadt, dev-platform, Firefox Dev
Thank you for continuing to keep try syntax working. I know I'm
holding back progress by not spending the time to figure out how to
convert `./mach try -b do -p win32-mingwclang,win64-mingwclang -u all
-t none` to fuzzy (maybe it's something like `./mach try fuzzy
"'mingwclang -talos"` ?).

-tom
> _______________________________________________
> firefox-dev mailing list
> firef...@mozilla.org
> https://mail.mozilla.org/listinfo/firefox-dev

James Graham

unread,
Jul 6, 2020, 2:00:51 PM7/6/20
to dev-pl...@lists.mozilla.org
On 06/07/2020 17:50, Tom Ritter wrote:
> Thank you for continuing to keep try syntax working. I know I'm
> holding back progress by not spending the time to figure out how to
> convert `./mach try -b do -p win32-mingwclang,win64-mingwclang -u all
> -t none` to fuzzy (maybe it's something like `./mach try fuzzy
> "'mingwclang -talos"` ?).

AFAICT `mach try fuzzy -full -q mingwclang`

One of the nice things about `mach try fuzzy` is that without a `-q`
argument you get a try-before-you-buy interface to select tasks. And you
can save the query as a preset to use as e.g. `mach try --preset
mingwclang`.

Andrew Halberstadt

unread,
Jul 15, 2020, 9:35:42 AM7/15/20
to dev-platform, Firefox Dev
This change has now merged to central. If you see errors about unrecognized
arguments when running |mach try|, you'll need to follow one of the options
above.
Reply all
Reply to author
Forward
0 new messages