Open
Bug 1621961
Opened 5 years ago
Updated 3 years ago
Make use of perf framework context
Categories
(Tree Management :: Treeherder, defect, P3)
Tree Management
Treeherder
Tracking
(Not tracked)
NEW
People
(Reporter: igoldan, Unassigned)
Details
(Keywords: good-first-bug)
Currently, the Compare results against another revision hyperlink from Job Details associated to perf job (e.g.) points to a Compare view that's not entirely setup.
The view points to one of the correct revisions, but it doesn't point to the correct perf framework. It always defaults to talos, even if the original perf job was from raptor.
We need to address this small issue.
|
Reporter | |
Comment 1•5 years ago
|
||
Kimberly, would you like to work on this task?
Flags: needinfo?(ksereduck)
|
||
Updated•5 years ago
|
Assignee: nobody → ksereduck
|
|
||
Comment 3•5 years ago
|
||
Just returning from leave, and trying to get caught up where I left off on onboarding. Unassigning
|
|
||
Updated•5 years ago
|
Assignee: ksereduck → nobody
|
||
Comment 4•5 years ago
|
||
Because this bug's Severity has not been changed from the default since it was filed, and it's Priority is P3 (Backlog,) indicating it has been triaged, the bug's Severity is being updated to S3 (normal.)
Severity: normal → S3
|
Assignee | |
Updated•3 years ago
|
Component: Treeherder: Job Triggering & Cancellation → TreeHerder
You need to log in
before you can comment on or make changes to this bug.
Description
•