1697261 - include full mach try command in push commit

Status: NEW

(Developer Infrastructure :: Try, enhancement, P3)

Description

[Andrew Erickson [:aerickson]]

It's great that the test command is logged, but I've had lots of issues recreating a try job another user has run. I think it's due to --full and --no-artifact, but it would be great if the exact command used was mentioned vs just the fuzzy query params.

Example: https://hg.mozilla.org/try/rev/3885fb0cd5ed7981aa1143f1dcc66739f98204a3

Running mach try with that fuzzy query will not generate the job set that was run for that push.

Comment 1

[Andrew Halberstadt [:ahal]]

Good idea! If not in the first line of the summary, it could go in the longer description. Another way of solving this particular problem is to allow pointing directly at a treeherder push. E.g, maybe something like:

./mach try again --from-treeherder <url>

or something like that.

Comment 2

[Mike Hommey [:glandium]]

Note that some of the things don't necessarily appear on the command line:

• If presets are used, the command line doesn't have the query
• When using the interactive mode, what's selected doesn't necessarily match the query
• --artifact is implied depending on mozconfig

Overall, the alternative in comment 1 would probably be more reliable, although it has downsides as well (if your own tree is significantly different, the list of tasks may not match, the chunking may be different, etc.).

Comment 3

[Andrew Erickson [:aerickson]]

For my particular issue of trying to match another user's push, I was getting the same set of jobs I just didn't see it due to the jobs being tier 3. I just had to click tier 3 to reveal the jobs.

I shouldn't be using what I see in the UI to tell if pushes are equivalent. I filed Bug 1697297 to show a total job count in treeherder. If I could see that both pushes had X jobs, then I'd know they're roughly equivalent (if the try commit looks similar) and might just search for UI buttons to push.