Closed
Bug 1283819
Opened 9 years ago
Closed 6 years ago
[tracking bug] - dashboard and/or tool changes to accommodate data needs of release management
Categories
(Tree Management :: Perfherder, task, P3)
Tree Management
Perfherder
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jmaher, Unassigned)
References
Details
(Keywords: meta)
I will use this bug to track our bugs related to dashboard and tooling for relman usage of the perf data.
A few thoughts, will file bugs when I feel it is more actionable:
* a list of tracking bugs for a revision, or maybe a way to query all bugs found in a time window/branch with a list of bugs/state and then nice links to the alerts
* a list of interesting revisions that we can use for comparing, ideally first/last builds of a specific firefox version on a train, likewise different release candidates
* update to either compare chooser or a new tool that can easily compare perf like alerts do for 2 arbitrary revisions
* modify e10s dashboard to accept revisions from above
* support comparison of >1 revision
* a high level dashboard that makes it easy to find e10s data, comparison between specific revisions, all bugs/alerts for a specific release
* possibly a way to bucketize the tests/data so it is clearer what is pageload, firefox UI, js, graphics, startup, etc.
| Reporter | ||
Comment 1•9 years ago
|
||
also to sort the list of bugs by severity, possibly we can do that with the list of alerts related to the bugs/release.
Comment 2•6 years ago
|
||
The thoughts/proposals from comment 0 have either been implemented, became outdated or have more recent, duplicate bugs (like the support comparison of >1 revision).
Closing this as resolved.
Updated•6 years ago
|
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Updated•6 years ago
|
Type: defect → task
You need to log in
before you can comment on or make changes to this bug.
Description
•