15
edits
TestEngineering/Performance/Sheriffing/Workflow: Difference between revisions
TestEngineering/Performance/Sheriffing/Workflow (view source)
Revision as of 13:15, 23 February 2024
, 23 February 2024→Sheriffing Firefox-Android Alerts: Adding more updated info
Bacasandrei (talk | contribs) |
Bacasandrei (talk | contribs) (→Sheriffing Firefox-Android Alerts: Adding more updated info) |
||
| Line 396: | Line 396: | ||
Lastly, backfilling on the mozilla-central side when a change is detected in a GeckoView commit is done with try runs. [https://wiki.mozilla.org/Performance/Fenix/Performance_reviews#Backfilling_to_determine_culprit_commit| You can find instructions for that here]. | Lastly, backfilling on the mozilla-central side when a change is detected in a GeckoView commit is done with try runs. [https://wiki.mozilla.org/Performance/Fenix/Performance_reviews#Backfilling_to_determine_culprit_commit| You can find instructions for that here]. | ||
=== How to triage a firefox-android alert === | |||
1. Read the graph, check for job gaps (browsertime & build_metrics): | |||
* click on the graph icon next to an alert item (usually the highest magnitude) | |||
a thin vertical line will show for all the alerts associated with the test, you need to make sure you’re looking at the right one by hovering or * clicking on the datapoint | |||
* click on the job link to go to treeherder job view | |||
* make sure you’re seeing the jobs from current revision back and look for gaps | |||
2. Trigger the jobs in the revisions in the gap (browsertime & build_metrics) | |||
* For every revision in the gap click “Add new jobs” and trigger the needed job | |||
3. Find the responsible push that caused the regression | |||
* If the regression is caused by a mozilla-central push, then you have to take the build id (Update GeckoView (Nightly) to 121.0.20231106094018.) and search for the revision in Buildhub | |||
* Build-metrics: file a generic performance regression | |||
* Browsertime: it should be an autoland alert to mark as downstream for | |||
4. If it’s caused by a firefox-android push then the process of filling a regression bug should be straight-forward - the default one from documentation. (browsertime & build_metrics) | |||
= Resources = | = Resources = | ||
* [https://wiki.mozilla.org/TestEngineering/Performance/FAQ FAQ] | * [https://wiki.mozilla.org/TestEngineering/Performance/FAQ FAQ] | ||