Alerts unable to retrigger because of the infra change
Categories
(Testing :: Performance, defect)
Tracking
(Not tracked)
People
(Reporter: alexandrui, Unassigned)
References
(Regression)
Details
(Keywords: regression)
The infra change on November 8th (Alert 23788) caused the inability to retrigger jobs from commits between 8-11 November.
Comment 1•5 years ago
|
||
The infra change is all grouped under the meta bug 1546801.
Updated•5 years ago
|
Updated•5 years ago
|
Comment 2•5 years ago
|
||
== Change summary for alert #23721 (as of Tue, 05 Nov 2019 18:12:09 GMT) ==
Regressions:
39% raptor-tp6-twitch-firefox-cold fcp linux64-shippable-qr opt 89.92 -> 125.42
30% raptor-tp6-apple-firefox-cold fcp windows10-64-shippable-qr opt 471.83 -> 613.50
10% raptor-tp6-apple-firefox-cold windows10-64-shippable-qr opt 602.07 -> 662.22
Improvements:
5% raptor-tp6-twitch-firefox fcp linux64-shippable-qr opt 79.77 -> 75.75
For up to date results, see: https://treeherder.mozilla.org/perf.html#/alerts?id=23721
Comment 3•5 years ago
|
||
The priority flag is not set for this bug.
:davehunt, could you have a look please?
For more information, please visit auto_nag documentation.
Comment 4•5 years ago
|
||
Bebe: Why does https://treeherder.mozilla.org/perf.html#/alerts?id=23721 link to this bug? I believe this should be closed as a duplicate of bug 1595381.
Updated•5 years ago
|
Updated•3 years ago
|
Description
•