Sheriffs have one overarching role: to ensure that the Chromium build infrastructure is doing its job of helping developers deliver good software. Every other sheriff responsibility flows from that one. In priority order, sheriffs need to ensure that:
As the sheriff, you not only have those responsibilities, but you have any necessary authority to fulfill them. In particular, you have the authority to:
TBRs were removed in Q1 2021.
For more information on Chromium Trunk Sheriffs, including How Tos, Swapping Shifts and rotation updates, please see Chromium Trunk Sheriffing
To be a sheriff, you must be both a Chromium committer and a Google employee. For more detailed sheriffing instructions, please see the internal documentation at go/chrome-sheriffing-how-to.
The currently oncall sheriffs can be viewed in the top-left corner of the Chromium Main Console. You can also get in touch with sheriffs using the #sheriffing Slack channel.
As part of their role, sheriffs will triage open test failures and flakes. If possible, they will identify a culprit CL and revert it; however, sometimes this is not feasible. In that case, sheriffs will assign these bugs to appropriate owners. They typically do this by looking for:
Pro-tip: Sheriffs, identify yourself in your comments, e.g., “[Sheriff] assigning to the test author for further triage.”
If you are assigned a bug by a sheriff, please don't pass the bug back to that person. Sheriffs have likely never seen the code before (or since), and are unlikely to be much help. Additionally, if >8 hours have passed, that person is no longer sheriff, and thus no longer responsible for triaging these bugs.
Instead, if you aren‘t the best owner for the bug, please help to triage it more appropriately, since you’re probably the test author, familiar with the test, or an OWNER. If have no idea who a good owner for the test is (or were assigned the bug in error*), you can reapply the
Sheriff-Chromium label and flip the status to
Untriaged; this will put it back in the sheriff queue for the next sheriff to take a look at. Please only do this as a last resort, since the next sheriff is unlikely to have any more information about the issue.
*If you believe you were assigned the bug in error, it might be worth finding out why the sheriff passed it to you, and remedying it if possible - e.g. by updating OWNERS files.