Closed
Bug 1840394
Opened 2 years ago
Closed 2 years ago
Chromium-as-Release builds not properly handled in Perfherder Compare View
Categories
(Tree Management :: Perfherder, defect, P2)
Tree Management
Perfherder
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: bas.schouten, Assigned: sparky)
References
()
Details
(Whiteboard: [fxp][operational])
When using Perfherder Compareview with application custom-car for viewing Chromium-as-Release numbers/developments (see included URL), you get the wrong graphs when clicking the graph buttons next to a metric.
It would also probably be good if the subtest compare view gave you an idea of the app you were looking at without having to check the URL bar.
Updated•2 years ago
|
Whiteboard: [fxp]
Updated•2 years ago
|
| Assignee | ||
Comment 1•2 years ago
|
||
PR for this is up: https://github.com/mozilla/treeherder/pull/7876
| Assignee | ||
Comment 2•2 years ago
|
||
Patch has been merged into Treeherder and will be available in the next deployment.
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
| Assignee | ||
Updated•2 years ago
|
Severity: -- → S3
Priority: -- → P1
| Assignee | ||
Updated•2 years ago
|
Assignee: nobody → gmierz2
Updated•4 months ago
|
Priority: P1 → P2
Updated•4 months ago
|
Whiteboard: [fxp] → [fxp][operational]
Updated•4 months ago
|
Severity: S3 → S2
You need to log in
before you can comment on or make changes to this bug.
Description
•