Google ChromeOS
6 boards ran 12,500 evaluations in the last 12 months. 453 first attempts failed; 294 passed on retry. 159 evaluations still failed after retries, most on Trogdor (SC7180).
The bench
One tape per board: evaluations per week, stacked by final outcome. Each tape has its own scale, topped by its busiest week, so compare boards by the totals beside their names. Failures sit on top as caps.
- Pass
- Passed on retry
- Lab
- Code
- Cancelled
- Unclassified
- Asurada (MT8192)MT81923,218Failures on 16 weeks
- Cherry (MT8195)MT81952,862Failures on 5 weeks
- Corsola (MT8186)MT81862,857Failures on 5 weeks
- Geralt (MT8188)MT8188379Failures on 2 weeks
- Rauru (MT8196)MT8196336No failures
- Trogdor (SC7180)SC71802,848Failures on 24 weeks
Changes with a failed boot on this board
Distinct change and patchset pairs whose evaluation on the board (Allow-CI+2 for TF-A, linked runs for TF-M) still failed its boot check after retries, out of pairs with a boot verdict. Only runs whose Jenkins lineage was captured can count, so each board shows the share of its evaluations linked to a change. Gerrit votes are not collected, so this is not a count of blocked changes.
Failed after retries
CI evaluations with a final code, lab or unclassified failure, newest first; 25 of 159 shown. Health checks and manual runs are never listed here.
Fleet health
Health checks from the last 7 days, whatever the window above. They are not CI results and never count towards any rate on this page. Check units means at least one unit's latest health check failed.
18 devices across 6 board types. Devices are units that ran any LAVA job, health checks included, in the last 30 days, whatever the window or project above. Every board type that is not retired counts, including those with health checks only.