Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(462)

Side by Side Diff: tools/perf/docs/perf_bot_sheriffing.md

Issue 2611203003: [Telemetry] Update perf bot health documentation to include handoff instructions. (Closed)
Patch Set: Created 3 years, 11 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View unified diff | Download patch
« no previous file with comments | « no previous file | no next file » | no next file with comments »
Toggle Intra-line Diffs ('i') | Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
OLDNEW
1 # Perf Bot Sheriffing 1 # Perf Bot Sheriffing
2 2
3 The perf bot sheriff is responsible for keeping the bots on the chromium.perf 3 The perf bot sheriff is responsible for keeping the bots on the chromium.perf
4 waterfall up and running, and triaging performance test failures and flakes. 4 waterfall up and running, and triaging performance test failures and flakes.
5 5
6 **[Rotation calendar](https://calendar.google.com/calendar/embed?src=google.com_ 2fpmo740pd1unrui9d7cgpbg2k%40group.calendar.google.com)** 6 **[Rotation calendar](https://calendar.google.com/calendar/embed?src=google.com_ 2fpmo740pd1unrui9d7cgpbg2k%40group.calendar.google.com)**
7 7
8 ## Key Responsibilities 8 ## Key Responsibilities
9 9
10 * [Handle Device and Bot Failures](#Handle-Device-and-Bot-Failures) 10 * [Handle Device and Bot Failures](#Handle-Device-and-Bot-Failures)
(...skipping 272 matching lines...) Expand 10 before | Expand all | Expand 10 after
283 **[Pri-1 bugs](https://bugs.chromium.org/p/chromium/issues/list?can=2&q=label%3A Performance-Sheriff-BotHealth+label%3APri-1)** 283 **[Pri-1 bugs](https://bugs.chromium.org/p/chromium/issues/list?can=2&q=label%3A Performance-Sheriff-BotHealth+label%3APri-1)**
284 should be pinged daily, and checked to make sure someone is following up. Pri-1 284 should be pinged daily, and checked to make sure someone is following up. Pri-1
285 bugs are for a red test (not yet disabled), purple bot, or failing device. Here 285 bugs are for a red test (not yet disabled), purple bot, or failing device. Here
286 is the [list of Pri-1 bugs that have not been pinged today](https://bugs.chromiu m.org/p/chromium/issues/list?can=2&q=label:Performance-Sheriff-BotHealth%20label :Pri-1%20modified-before:today-1&sort=modified). 286 is the [list of Pri-1 bugs that have not been pinged today](https://bugs.chromiu m.org/p/chromium/issues/list?can=2&q=label:Performance-Sheriff-BotHealth%20label :Pri-1%20modified-before:today-1&sort=modified).
287 287
288 **[Pri-2 bugs](https://bugs.chromium.org/p/chromium/issues/list?can=2&q=label%3A Performance-Sheriff-BotHealth+label%3APri-2)** 288 **[Pri-2 bugs](https://bugs.chromium.org/p/chromium/issues/list?can=2&q=label%3A Performance-Sheriff-BotHealth+label%3APri-2)**
289 are for disabled tests. These should be pinged weekly, and work towards fixing 289 are for disabled tests. These should be pinged weekly, and work towards fixing
290 should be ongoing when the sheriff is not working on a Pri-1 issue. Here is the 290 should be ongoing when the sheriff is not working on a Pri-1 issue. Here is the
291 [list of Pri-2 bugs that have not been pinged in a week](https://bugs.chromium.o rg/p/chromium/issues/list?can=2&q=label:Performance-Sheriff-BotHealth%20label:Pr i-2%20modified-before:today-7&sort=modified). 291 [list of Pri-2 bugs that have not been pinged in a week](https://bugs.chromium.o rg/p/chromium/issues/list?can=2&q=label:Performance-Sheriff-BotHealth%20label:Pr i-2%20modified-before:today-7&sort=modified).
292 292
293 ## Shift Hand-off
294
295 At the end of your shift you should send out a message to the next sheriff It
296 should detail any ongoing issues you are trying to resolve. This can contain new
297 bugs you have filed and bisects you are waiting to finish. If there has been any
298 significant updates on older issues that the next sheriff should know about they
299 should also be included. This will greatly decrease the amount of time needed
300 for the next sheriff to come up to speed.
301
302 There is also a weekly debrief that you should see on your calendar titled
303 **Weekly Speed Sheriff Retrospective**. For this meeting you should prepare
304 any highlights or lowlights from your sheriffing shift as well as any other
305 feedback you may have that could improve future sheriffing shifts.
306
293 <!-- Unresolved issues: 307 <!-- Unresolved issues:
294 1. Do perf sheriffs watch the bisect waterfall? 308 1. Do perf sheriffs watch the bisect waterfall?
295 2. Do perf sheriffs watch the internal clank waterfall? 309 2. Do perf sheriffs watch the internal clank waterfall?
296 --> 310 -->
OLDNEW
« no previous file with comments | « no previous file | no next file » | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698