Confirmed users
24
edits
Sheriffing/How To/Beta simulations: Difference between revisions
m
edit moz-phab command
m (changed the mercurial commands to git ones) |
m (edit moz-phab command) |
||
| Line 17: | Line 17: | ||
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/> | ||
<code>moz-phab patch D<number> --apply-to | <code>moz-phab patch D<number> --apply-to @ </code><br/> | ||
The patch number is mentioned at the top of the phabricator page for the patch.<br/> | The patch number is mentioned at the top of the phabricator page for the patch.<br/> | ||
If the dependencies should not be imported, e.g. because they are not needed, they can be skipped like this:<br/> | If the dependencies should not be imported, e.g. because they are not needed, they can be skipped like this:<br/> | ||
<code>moz-phab patch D<number> --apply-to | <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>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> | **<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> | ||