97
edits
TestEngineering/Performance/Sheriffing/Workflow: Difference between revisions
Jump to navigation
Jump to search
TestEngineering/Performance/Sheriffing/Workflow (view source)
Revision as of 12:57, 30 March 2023
, 30 March 2023→Special Cases: Add information for sheriffing firefox-android alerts.
Alexandrui (talk | contribs) |
(→Special Cases: Add information for sheriffing firefox-android alerts.) |
||
| Line 298: | Line 298: | ||
If the push that has been identified as the culprit has multiple revisions and bug ids linked to it, the sheriff can fill in the "Regressed By" field for each of the bugs with the value of the filed bug for the associated alert. <br/> | If the push that has been identified as the culprit has multiple revisions and bug ids linked to it, the sheriff can fill in the "Regressed By" field for each of the bugs with the value of the filed bug for the associated alert. <br/> | ||
TODO: add screenshot for example [https://treeherder.mozilla.org/jobs?repo=autoland&revision=88a481adf83070d1cdcc2bb074f6545b5dfe97e7&group_state=expanded&selectedTaskRun=GAP1DzYETPawhJhP1WkzGw.0/ alert] | TODO: add screenshot for example [https://treeherder.mozilla.org/jobs?repo=autoland&revision=88a481adf83070d1cdcc2bb074f6545b5dfe97e7&group_state=expanded&selectedTaskRun=GAP1DzYETPawhJhP1WkzGw.0/ alert] | ||
== Sheriffing Firefox-Android Alerts == | |||
The [https://treeherder.mozilla.org/jobs?repo=firefox-android| firefox-android repo] (which contains fenix) also produces alerts at a lower cadence (~6 days after a change is triggered). | |||
Sheriffing this branch is the same as autoland in that you'll need to do backfills on the firefox-android branch to determine a culprit commit. Once you find a culprit commit, then file a bug in bugzilla as usual, and needinfo the author of the commit. | |||
If you find a commit that has no clear author [https://treeherder.mozilla.org/jobs?repo=firefox-android&revision=96420c198887c5148a2a5b80b947c6891403d0f2| such as this one], then you'll have one of two options depending on the type of commit it is: | |||
* If the commit message mentions '''Geckoview''' or something related to mozilla-central, then needinfo '''Bryan Clark [:bclark]''' in the bug for the alert. | |||
* If the commit message doesn't mention '''Geckoview''' and has no clear author, [https://treeherder.mozilla.org/jobs?repo=firefox-android&revision=60eba6f35766d898964c409eeeacd7573812c364| like this commit], then needinfo '''Joe Mahon [:jmahon]''' in the bug for the alert. | |||
Check to see if there might be an associated Geckoview alert that was produced on autoland when there's an alert produced on firefox-android. If there was then you can associated the two alert bugs with a '''See Also''' entry. | |||
Lastly, backfilling on the mozilla-central side when a change is detected in a Geckoview commit is done with try runs, and [https://wiki.mozilla.org/Performance/Fenix/Performance_reviews#Backfilling_to_determine_culprit_commit| you can find instructions for that here]. | |||
= Resources = | = Resources = | ||
* [https://wiki.mozilla.org/TestEngineering/Performance/FAQ FAQ] | * [https://wiki.mozilla.org/TestEngineering/Performance/FAQ FAQ] | ||