[mach-try-perf] Use UUID/markers to associate a base try run with a new try run
Categories
(Testing :: Performance, task, P2)
Tracking
(Not tracked)
People
(Reporter: sparky, Unassigned)
References
(Blocks 2 open bugs)
Details
(Whiteboard: [fxp])
This bug is for using something like UUIDs/markers in the commit message of mach-try-perf try runs and having perfcompare use those to match the new/base revisions to each other.
The upcoming hg->git changes will have an impact on mach try perf by eventually removing the ability to get remote revisions locally (everything will be through lando). Also, new setups will no longer have access to the remote revision locally sooner than when support for it is completely removed. So this change will be needed soon.
Two main things will need to be done here:
(1) Add a UUID to the try run run commit messages.
(2) Have perfcompare match base, and new try runs based on this UUID.
For (1), it's relatively trivial to implement it mach-try-perf. Most of the work here will likely be on the perfcompare side.
Updated•26 days ago
|
Reporter | ||
Updated•26 days ago
|
Description
•