13
edits
TestEngineering/Performance/Sheriffing/Workflow: Difference between revisions
Jump to navigation
Jump to search
TestEngineering/Performance/Sheriffing/Workflow (view source)
Revision as of 10:41, 26 February 2024
, 26 February 2024→Special Cases: added special case for build_metrics
Bacasandrei (talk | contribs) (→Alerts caused by modifying release flags (EARLY_BETA_OR_EARLIER) / bumping the Firefox version: Adding more details.) |
Bacasandrei (talk | contribs) (→Special Cases: added special case for build_metrics) |
||
| Line 436: | Line 436: | ||
*''most of the time, when a change is pushed to autoland, it is also pushed to mozilla-central during the same day'' | *''most of the time, when a change is pushed to autoland, it is also pushed to mozilla-central during the same day'' | ||
*''on mozilla-beta the change is merged after ~ 6 weeks'' | *''on mozilla-beta the change is merged after ~ 6 weeks'' | ||
== build_metrics special cases == | |||
# '''''decision''''' alerts usually are just spikes and not relevant, which is why we are setting them as ''invalid''. In the case that, by looking at the coresponding graph, the regression wasn't improved / fixed, then check with the other sheriffs in the Sheriffs of Performance channel on Element since it might be a cause of concern. | |||
# '''''instrumented''''' in the Tags & Options column should be set as ''invalid''. Alerting will be deactivated for these tests in the future. | |||
== Alert caused by a backout == | == Alert caused by a backout == | ||