Board test coverage
Which boards in TF CI were seen testing which firmware branch, and with what result. Test results for the last 30 days; older history is at job level only.
Data as of 29 Oct 2026, 09:00 UTCLast synced:LAVA 29 Oct 2026, 09:00 UTCJenkins 29 Oct 2026, 09:01 UTCS3 export 7 Oct 2026, 09:53 UTC
Window
Runs
Names
Project
TF-A
Scroll the matrix sideways to see every branch.
TF-M
Scroll the matrix sideways to see every branch.
How to read the matrix
- Pass
- Code: a test failed, or the job failed after boot
- Lab: the run did not complete for lab reasons
- Cancelled
- Unclassified: the cause was not recorded
- Declared in job definitions, not observed in this window. Declared never means passed.
- No observation: we did not see this run, which is not the same as unsupported
- Last 10 evaluations, oldest on the left. Short means pass, tall means a problem; hatched is the lab, solid is the code; a capped short tick passed on retry.
Rate is evaluations that passed after retries, out of evaluations that passed or failed in the code. With fewer than 5 of those it is shown as a fraction. The base n counts pass and code verdicts. The count beside the rate includes all evaluations, including lab, cancelled and unclassified.
Not shown here: FVP and QEMU testing, which runs in TuxSuite, and Allow-CI +1 runs, which are build-only and never reach a board. Their absence from this page is not a coverage gap.
12 months of CI attempts
Job level: attempts per month and how many completed. Test-case detail exists only for the live window. Months without data are drawn as gaps, never as zero.
TF-A
- CI attempts per month
- Complete attempts, %
Test-case detail: September 2026 to October 2026.
TF-M
- CI attempts per month
- Complete attempts, %
Test-case detail: September 2026 to October 2026.