Confirmed users
24
edits
Sheriffing/How To/Beta simulations: Difference between revisions
Jump to navigation
Jump to search
changed the mercurial commands to git ones
m (increased version numbers (Nightly = 141, Beta = 140)) |
(changed the mercurial commands to git ones) |
||
| Line 13: | Line 13: | ||
== SILENCING KNOWN PERMAFAILS == | == SILENCING KNOWN PERMAFAILS == | ||
* If you need to import patches or backout something, make sure to start with an up to date local copy: | * If you need to import patches or backout something, make sure to start with an up to date local copy: | ||
**<code> | **<code>git checkout main</code> | ||
**<code> | **<code>git pull</code> | ||
If a permanent failure is known from previous simulations but not fixed according to the bug, it's helpful to prevent this failure to reduce the need for failure classifications and to provide a better picture when one looks at the whole beta simulation. These are the possibilities: | If a permanent failure is known from previous simulations but not fixed according to the bug, it's helpful to prevent this failure to reduce the need for failure classifications and to provide a better picture when one looks at the whole beta simulation. These are the possibilities: | ||
*'''Fix on phabricator''': If there is a fix hosted on phabricator, import it to migitate the issue. By default, the <code>moz-phab patch</code> command will import all revisions a patch depends on (has as ancestors). If it's a patch series, import the last patch to also auto-import the previous ones:<br/> | *'''Fix on phabricator''': If there is a fix hosted on phabricator, import it to migitate the issue. By default, the <code>moz-phab patch</code> command will import all revisions a patch depends on (has as ancestors). If it's a patch series, import the last patch to also auto-import the previous ones:<br/> | ||
| Line 22: | Line 22: | ||
<code>moz-phab patch D<number> --apply-to . --skip-dependencies</code><br/> | <code>moz-phab patch D<number> --apply-to . --skip-dependencies</code><br/> | ||
*'''Back out change causing failure''': If the bug about the perma failure mentions the bug whose check-ins cause the failures, those can be backed out '''locally''' for the beta simulation: | *'''Back out change causing failure''': If the bug about the perma failure mentions the bug whose check-ins cause the failures, those can be backed out '''locally''' for the beta simulation: | ||
**<code> | **</code>git revert <git hash></code> (if more than one hash needs reverting use <code>git revert first_git_hash~1..last_git_hash --no-edit</code> and then squash them) <span style="color:#14866d">//The revisions of the bug whose backout fixes the issue. The backout revisions will have to be deleted with <code>git reset --hard origin/main</code> once the beta simulations have been created.<span> | ||
*'''Disable failing test''': Similar to how frequently failing tests are disabled. Disadvantage: Additional failures or changes in the failure message in the test get missed. | *'''Disable failing test''': Similar to how frequently failing tests are disabled. Disadvantage: Additional failures or changes in the failure message in the test get missed. | ||