| OLD | NEW |
|---|
| (Empty) |
| 1 # Triaging Data Stoppage Alerts | |
| 2 | |
| 3 ## What is a data stoppage alert? | |
| 4 A data stoppage alert is a new type of alert on the perf dashboard. Instead of a | |
| 5 performance regression, it indicates that the dashboard is no longer receiving | |
| 6 data for the given monitored test. A bug created from a data stoppage alert has | |
| 7 a subject starting with **“No data received for…”**. | |
| 8 | |
| 9 ## How to triage data stoppage alerts | |
| 10 | |
| 11 ### Check if the alert is recovered. | |
| 12 Look at the graph and see if there are new points, if so, mark the alert | |
| 13 **ignored**. | |
| 14 | |
| 15 ### File a bug | |
| 16 Use the triage dialog to file a bug about the failure, and track your | |
| 17 investigation. Cc the owner of the benchmark from | |
| 18 [go/chrome-benchmarks](http://goto.google.com/chrome-benchmarks). | |
| 19 | |
| 20 ### Get the logs | |
| 21 Each alert has a debug button at the right-hand side of the table. It tries to | |
| 22 automatically find the last successful build and the first failed build. To get | |
| 23 the logs: | |
| 24 * First try the *"Logs"* link from *"Next revison built"* (this should be the | |
| 25 first failed revision). Sometimes this can't be generated properly, so it | |
| 26 may not work. | |
| 27 * Next try the *"Buildbot status page"* link from *"Next revision built"*. | |
| 28 This should take you to the next build. **If this page 404s, it's possible | |
| 29 the builder was taken down.** Check the waterfall. | |
| 30 | |
| 31 Once you have the logs, put the link in the bug and also paste relevant snippets | |
| 32 about the failure (error logs) in the bug. | |
| 33 | |
| 34 ### Check for suspicious changes. | |
| 35 It has a link to *"View commit log from rXXX to rYYY"*, click the link to view | |
| 36 CLs in the range. Look through the range for test disables, telemetry/catapult | |
| 37 changes, and changes to the code under test. If you see a CL that looks like a | |
| 38 likely culprit, cc the author in the bug. | |
| 39 | |
| 40 ### Kick off a bisect. | |
| 41 If the test is failing on the *"Next revision built"*, bisect may be able to | |
| 42 narrow down the culprit. Go to the graph, click a data point, and click the | |
| 43 bisect button in the tooltip. **You'll need to change the values for return_code | |
| 44 bisect as follows**: | |
| 45 * **Bug ID**: Make sure to fill in the ID of the bug you just filed. | |
| 46 Otherwise the bisect will not update it. | |
| 47 * **Earlier revision**: Change this to the *"Last revision uploaded"* from the | |
| 48 debug button dialog. | |
| 49 * **Later revision**: Change this to the *"Next revision built"* from the | |
| 50 debug button dialog. | |
| 51 * **Bisect mode**: Change this to **return_code** | |
| OLD | NEW |
|---|
Chromium Code Reviews
Issue 2972043002:
Remove documentation on stoppage alerts. (Closed)
