TestEngineering/Performance/Sheriffing/Workflow: Difference between revisions

(→‎Special Cases: Jobs failing to run description)
Line 423: Line 423:
== Alerts caused by modifying release flags (EARLY_BETA_OR_EARLIER) / bumping the Firefox version ==
== Alerts caused by modifying release flags (EARLY_BETA_OR_EARLIER) / bumping the Firefox version ==
These alerts are generated on mozilla-beta and have no bugs associated with the revisions:
These alerts are generated on mozilla-beta and have no bugs associated with the revisions:
# Check the milestone version by looking into the changeset details.  
# Check the milestone version by looking into the changeset details.
# Clone bug https://bugzilla.mozilla.org/show_bug.cgi?id=1879080. <br/>
# Check if there was already a bugzilla bug created for this particualr milestone version.
# If not, then clone the following bug https://bugzilla.mozilla.org/show_bug.cgi?id=1879080. <br/>
# Leave a comment with the alert summary you were investigating.
Comment 0 could include the following information: <br/>
Comment 0 could include the following information: <br/>
''There were some alerts generated on mozilla-beta, that have no bugs associated with the revisions. <br/>''
''There were some alerts generated on mozilla-beta, that have no bugs associated with the revisions. <br/>''
Line 434: 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''


== Alert caused by a backout ==
== Alert caused by a backout ==
15

edits