If you do lots of try pushes it’s worth learning to star oranges using the keyboard instead of the mouse. It’s much faster that way.
The important keystrokes are as follows.
- ‘j’ and ‘n’ move focus to the next unstarred failure. (‘k’ and ‘p’ move focus to the previous unstarred failure.)
- Space adds the selected failure to the pinboard.
- Ctrl-Enter stars all jobs in the pinboard.
So a typical keystroke sequence to star multiple jobs would be: j, space, j, space, j, space, ctrl-enter. Between each j and space you should, of course, check that the failure matches an existing one.
This information, along with lots of other interesting tidbits, is in the Treeherder User Guide.
Thank you to Phil Ringnalda for teaching me this.
I have a patch that’s ready to land. I wanted to ensure that it compiles on all platforms. I also wanted to ensure that it passes all tests, but I felt that running all the tests on one of the tier 1 platforms was enough.
There’s no way to specify this combination in a single try server push, but I realized I could do it with two separate pushes. TryChooser told me that Linux64 was the least-loaded platform, so I did a try run with all the tests on that platform:
try: -b do -p linux64 -u all -t none
And then I did a try run that did builds (but no tests) on all platforms except Linux64:
try: -b do -p linux,macosx64,win32,android,android-armv6,android-noion,ics_armv7a_gecko,panda,otoro,unagi -u none -t none
Interesting. I wonder if this is a combination that other people have considered.