Closed
Bug 1496321
Opened 6 years ago
Closed 5 years ago
Alert summaries with unknown revisions
Categories
(Tree Management :: Perfherder, enhancement, P1)
Tree Management
Perfherder
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: igoldan, Assigned: sclements)
References
Details
For at least the last 2 weeks, occasional alert summaries with "Unknown revision(s)" started to show up. This smells like a bug, so we need to investigate & fix this issues. Examples: https://treeherder.mozilla.org/perf.html#/alerts?id=16342 https://treeherder.mozilla.org/perf.html#/alerts?id=16386
Reporter | ||
Comment 1•6 years ago
|
||
I noticed this happens when we're looking over them from the Alerts page: https://treeherder.mozilla.org/perf.html#/alerts?status=9&framework=1&hideDwnToInv=1&page=1
Reporter | ||
Comment 2•6 years ago
|
||
(In reply to Ionuț Goldan [:igoldan], Performance Sheriffing from comment #1) > I noticed this happens when we're looking over them from the Alerts page: > https://treeherder.mozilla.org/perf.html#/ > alerts?status=9&framework=1&hideDwnToInv=1&page=1 This may be just a Angular/Javascript issue.
Assignee | ||
Comment 3•5 years ago
|
||
I noticed this also while converting the Alerts table header (there was a code comment in the alerts partial that suggested the red "Unknown revision(s)" should only show up in development mode). After investigating, it turns out the revision information for those alerts isn't being returned by the Push API because there is a default of count=10
set for the API. This will be remedied by explicitly setting the count param accordingly (since we're querying for multiple push_ids at a time). I'll include the fix in my next conversion PR.
Assignee | ||
Updated•5 years ago
|
Assignee: nobody → sclements
Assignee | ||
Updated•5 years ago
|
Status: NEW → ASSIGNED
Assignee | ||
Comment 4•5 years ago
|
||
This has been fixed in this pr: https://github.com/mozilla/treeherder/pull/5005
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•