This page can be found at: g.co/bugatrooper
Have an issue with a piece of build infrastructure? Our troopers are here to help.
Oncall hours: we cover working hours in the Pacific timezone:
Issues in EMEA are handled on a best-effort basis by volunteers. See here (internal link) for contact information.
If you are contacting a trooper to see if there is an issue with a service, visit the ChOps Status Dashboard first. If the “Current Status” of the service shows red/yellow, that means there is a known disruption or outage, and the Trooper is already aware. No need to contact us further!
The primary way to contact a trooper is via crbug.com using the templates and priorities established below. If you need to find the current trooper, check build.chromium.org, or vi/chrome_infra (internal link). If crbug.com is down and you are unable to file a bug, please contact the team on firstname.lastname@example.org.
If you know your issue is with the physical hardware, or otherwise should be handled by the Systems team, please follow their Rules of Engagement.
For fastest response, please use the provided templates:
Also make sure to include the machine name (e.g. build11-m1) as well as the waterfall name (Builder: Win).
Priorities are set using the
Pri=N label. Use the following as your guideline:
Status will be tracked using the Status field, with the ‘owner’ field unset. The trooper queue relies on the ‘owner’ field being unset to track issues properly, with troopers setting the owners field for particularly long-running issues. Please do not assign issues to the trooper directly, doing so may actually increase the time taken to respond to an issue. Behind the scenes, our Troopers will review and triage the bug, as-needed, to corresponding Chrome Operations teams to be addressed.
All requests should contain the “Infra-Troopers” label such that we can properly triage the request and to indicate that this is user-filed.
Please file a bug using the Master restart requests bug template. This is preferred method if you are not a Googler, or not a committer in
infradata/master-manager repo. This is also a preferred method for large masters like
tryserver.chromium.*, to avoid duplicate restart requests and unintended downtime during peak hours.
Master restarts are handled by master manager and only require running a single command that mails a CL to schedule the restart.
depot_tools in your path, run:
# Get an auth token for your @google.com account if you don't already have one. depot-tools-auth login https://chromereviews.googleplex.com # The cit restart syntax is: # cit restart <waterfall name> -r <current trooper> [-b <bug number>] # # e.g. To restart the chromium.fyi master in 15 minutes for bug 123, with # trooper joe on duty: cit restart chromium.fyi -r joe -b 123
Note: if you‘re not in the committers list CQ will try it first and you’ll have to ping the trooper to get an lgtm. The master will be restarted at the requested time, or once the CL lands, whichever comes later.
If you're having trouble you can file a bug with the trooper using the Master restart requests bug template.
Troopers provide full time coverage with the expected response times outlined above during the Pacific work day. Other times support is provided best-effort.
View the current trooper queue.
Other available team trooper queues within Chrome Operations.
Common Non-Trooper Requests: