| OLD | NEW |
| 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 426 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... |
| 437 of this. The type name of the failing device can be found by searching for the | 437 of this. The type name of the failing device can be found by searching for the |
| 438 value of `ro.product.model` under the `provision_devices` step of the failing | 438 value of `ro.product.model` under the `provision_devices` step of the failing |
| 439 bot. | 439 bot. |
| 440 | 440 |
| 441 Disabling CLs can be TBR-ed to anyone in [tools/perf/OWNERS](https://code.google
.com/p/chromium/codesearch#chromium/src/tools/perf/OWNERS), | 441 Disabling CLs can be TBR-ed to anyone in [tools/perf/OWNERS](https://code.google
.com/p/chromium/codesearch#chromium/src/tools/perf/OWNERS), |
| 442 but please do **not** submit with NOTRY=true. | 442 but please do **not** submit with NOTRY=true. |
| 443 | 443 |
| 444 ### Disabling Other Tests | 444 ### Disabling Other Tests |
| 445 | 445 |
| 446 Non-telemetry tests are configured in [chromium.perf.json](https://code.google.c
om/p/chromium/codesearch#chromium/src/testing/buildbot/chromium.perf.json) **But
do not manually edit this file.** | 446 Non-telemetry tests are configured in [chromium.perf.json](https://code.google.c
om/p/chromium/codesearch#chromium/src/testing/buildbot/chromium.perf.json) **But
do not manually edit this file.** |
| 447 Update tools/perf/generate_perf_json.py to disable the test and rerun script to | 447 Update tools/perf/generate_perf_data.py to disable the test and rerun script to |
| 448 generate the new chromium.perf.json file. | 448 generate the new chromium.perf.json file. |
| 449 You can TBR any of the per-file OWNERS, but please do **not** submit with | 449 You can TBR any of the per-file OWNERS, but please do **not** submit with |
| 450 NOTRY=true. | 450 NOTRY=true. |
| 451 | 451 |
| 452 ## Follow up on failures | 452 ## Follow up on failures |
| 453 | 453 |
| 454 **[Pri-0 bugs](https://bugs.chromium.org/p/chromium/issues/list?can=2&q=label%3A
Performance-Sheriff-BotHealth+label%3APri-0)** | 454 **[Pri-0 bugs](https://bugs.chromium.org/p/chromium/issues/list?can=2&q=label%3A
Performance-Sheriff-BotHealth+label%3APri-0)** |
| 455 should have an owner or contact on speed infra team and be worked on as top | 455 should have an owner or contact on speed infra team and be worked on as top |
| 456 priority. Pri-0 generally implies an entire waterfall is down. | 456 priority. Pri-0 generally implies an entire waterfall is down. |
| 457 | 457 |
| (...skipping 18 matching lines...) Expand all Loading... |
| 476 | 476 |
| 477 There is also a weekly debrief that you should see on your calendar titled | 477 There is also a weekly debrief that you should see on your calendar titled |
| 478 **Weekly Speed Sheriff Retrospective**. For this meeting you should prepare | 478 **Weekly Speed Sheriff Retrospective**. For this meeting you should prepare |
| 479 any highlights or lowlights from your sheriffing shift as well as any other | 479 any highlights or lowlights from your sheriffing shift as well as any other |
| 480 feedback you may have that could improve future sheriffing shifts. | 480 feedback you may have that could improve future sheriffing shifts. |
| 481 | 481 |
| 482 <!-- Unresolved issues: | 482 <!-- Unresolved issues: |
| 483 1. Do perf sheriffs watch the bisect waterfall? | 483 1. Do perf sheriffs watch the bisect waterfall? |
| 484 2. Do perf sheriffs watch the internal clank waterfall? | 484 2. Do perf sheriffs watch the internal clank waterfall? |
| 485 --> | 485 --> |
| OLD | NEW |