Buildbot/Talos/Sheriffing: Difference between revisions

m
→‎Filing a bug: - June 2016 update
m (→‎Investigating the alert: - June 2016 update)
m (→‎Filing a bug: - June 2016 update)
Line 91: Line 91:


= Filing a bug =
= Filing a bug =
A lot of work is being done inside of Alert Manager to make filing a bug easier, As each bug has unique attributes it is hard to  handle this in a programmatic way, but we can do our best.  In fact, there is a 'File bug' clickable link which is underneath each Revision in Alert Manager.  Clicking it will bring up a popup with a suggested summary and description for the bug.
A lot of work has been done inside of Perfherder to make filing a bug easier, As each bug has unique attributes it is hard to  handle this fully programattic, but we can do our best.  In fact, there is a 'File bug' clickable link which is underneath each Alert Summary section in Perfherder Alerts.  Clicking it will bring you to bugzilla with as many fields filled in as possible.


Here are some guidelines for filing a bug:
Here are some things to check/verify when filing a bug:
* Product/Component - this should be the same as the bug which is the root cause, if >1 bug, file in "[[https://bugzilla.mozilla.org/enter_bug.cgi?product=Testing&component=Talos Testing :: Talos]]"
* Product/Component - this should be the same as the bug which is the root cause, if >1 bug, file in [https://bugzilla.mozilla.org/enter_bug.cgi?product=Testing&component=Talos Talos]
* Dependent/Block bugs - For a new bug, add the [[https://wiki.mozilla.org/Buildbot/Talos/Sheriffing#Tracking_bugs tracking bug]] and root cause bug(s) as blocking this bug
* Dependent/Block bugs - For a new bug, add the [[https://wiki.mozilla.org/Buildbot/Talos/Sheriffing#Tracking_bugs tracking bug]] (for the current version) and root cause bug(s) as blocking this bug
* CC list - cc :jmaher, :avih, patch author(s) and reviewer(s), and owner of the tests as documented on the [[https://wiki.mozilla.org/Buildbot/Talos/Tests talos tests wiki]]  
* CC list - cc :jmaher, :avih, :wlach, :avih, patch author(s) and reviewer(s), and owner of the tests as documented on the [[https://wiki.mozilla.org/Buildbot/Talos/Tests talos tests wiki]]  
* Summary of bug should follow this pattern (should be suggested correctly):
* Summary of bug should have a check to make sure the revision is accurate
  %xx <platform> <test> regression on <branch> (v.<xx>) Date, from push <revision>
* The description is auto suggested as well, please verify the revision here
* The description is auto suggested as well, this should be good, but do make sure it makes sense


As a note, the generated description refers the patch author to [[https://wiki.mozilla.org/Buildbot/Talos/RegressionBugsHandling guidelines and expectations]] for them about how and when to respond.


As a note, the generated description refers the patch author to [[https://wiki.mozilla.org/Buildbot/Talos/RegressionBugsHandling guidelines and expectations]] for them about how and when to respond.
Once a bug is filed it is a good idea to do a few things in another comment:
1) provide a link to compare view to show you have done retriggers and believe this is valid
2) needinfo the patch author (if many patch authors, needinfo :jmaher)
3) mention how confident you are in the regression (more confidence if you have a lot of retriggers and there is only one patch, less confident if you are waiting on backfilling data, retriggers, try runs, etc.)


= Other common tasks =
= Other common tasks =
Confirmed users
3,376

edits