| 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](#botfailures) | 10 * [Handle Device and Bot Failures](#Handle-Device-and-Bot-Failures) |
| 11 * [Handle Test Failures](#testfailures) | 11 * [Handle Test Failures](#Handle-Test-Failures) |
| 12 * [Follow up on failures](#followup) | 12 * [Follow up on failures](#Follow-up-on-failures) |
| 13 | 13 |
| 14 ## Understanding the Waterfall State | 14 ## Understanding the Waterfall State |
| 15 | 15 |
| 16 Everyone can view the chromium.perf waterfall at | 16 Everyone can view the chromium.perf waterfall at |
| 17 https://build.chromium.org/p/chromium.perf/, but for Googlers it is recommended | 17 https://build.chromium.org/p/chromium.perf/, but for Googlers it is recommended |
| 18 that you use the url https://uberchromegw.corp.google.com/i/chromium.perf/ inste
ad. | 18 that you use the url https://uberchromegw.corp.google.com/i/chromium.perf/ inste
ad. |
| 19 The reason for this is that in order to make the performance tests as realistic
as | 19 The reason for this is that in order to make the performance tests as realistic
as |
| 20 possible, the chromium.perf waterfall runs release official builds of Chrome. | 20 possible, the chromium.perf waterfall runs release official builds of Chrome. |
| 21 But the logs from release official builds may leak info from our partners that | 21 But the logs from release official builds may leak info from our partners that |
| 22 we do not have permission to share outside of Google. So the logs are available | 22 we do not have permission to share outside of Google. So the logs are available |
| (...skipping 254 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... |
| 277 | 277 |
| 278 **[Pri-2 bugs](https://bugs.chromium.org/p/chromium/issues/list?can=2&q=label%3A
Performance-Sheriff-BotHealth+label%3APri-2)** | 278 **[Pri-2 bugs](https://bugs.chromium.org/p/chromium/issues/list?can=2&q=label%3A
Performance-Sheriff-BotHealth+label%3APri-2)** |
| 279 are for disabled tests. These should be pinged weekly, and work towards fixing | 279 are for disabled tests. These should be pinged weekly, and work towards fixing |
| 280 should be ongoing when the sheriff is not working on a Pri-1 issue. Here is the | 280 should be ongoing when the sheriff is not working on a Pri-1 issue. Here is the |
| 281 [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). | 281 [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). |
| 282 | 282 |
| 283 <!-- Unresolved issues: | 283 <!-- Unresolved issues: |
| 284 1. Do perf sheriffs watch the bisect waterfall? | 284 1. Do perf sheriffs watch the bisect waterfall? |
| 285 2. Do perf sheriffs watch the internal clank waterfall? | 285 2. Do perf sheriffs watch the internal clank waterfall? |
| 286 --> | 286 --> |
| OLD | NEW |
|---|
Chromium Code Reviews
Issue 2467283006:
Clarify documentation on reporting bad bisects and fix anchor links. (Closed)
