Closed
Bug 1529090
Opened 5 years ago
Closed 5 months ago
No way to easily examine all the performance data for a try push
Categories
(Tree Management :: Perfherder, enhancement, P3)
Tree Management
Perfherder
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: bzbarsky, Unassigned)
References
Details
(Whiteboard: [fxp][lang=js][lang=py])
Once we have bug 1529048 in place, the next step is having a way to examine such a try push in perfherder for performance changes.
Right now that involves going through a long dropdown of test suites, loading them one at a time and examining one at a time. This is pretty time-consuming and error-prone (e.g. easy to miss one of the options in that dropdown).
It would be better if we had a perfherder view for all the results in a try push that are significantly different from the baseline.
|
||
Updated•5 years ago
|
Priority: -- → P3
|
|
||
Updated•5 years ago
|
Whiteboard: [lang=js][lang=py]
|
||
Comment 1•5 months ago
•
|
||
This sounds like PerfCompare / Compare View. @carla do you think we can close this as FIXED or WORKSFORME?
Flags: needinfo?(csevere)
Whiteboard: [lang=js][lang=py] → [fxp][lang=js][lang=py]
|
||
Updated•5 months ago
|
|
||
Comment 2•5 months ago
|
||
Yes, we can close as fixed.
Status: NEW → RESOLVED
Closed: 5 months ago
Flags: needinfo?(csevere)
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•