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, 12:21 UTCLast synced:LAVA 29 Oct 2026, 12:21 UTCJenkins 29 Oct 2026, 12:23 UTCS3 export 7 Oct 2026, 09:53 UTC
Window
Runs
Names
Project
TF-A
TF-A boards by branch and suite, last 30 days, branch and nightly.
master | LTS 2.14 | LTS 2.12 | LTS 2.10 | LTS 2.8 | integration | Unattributed | |
|---|---|---|---|---|---|---|---|
Arm | |||||||
juno22 observed devices, Boot, 14.4 checks | |||||||
lava | |||||||
0_shutdown, shutdown | |||||||
TFTF, tftf | |||||||
0_tftf-boot-banner, 0_tftf-exit, 0_tftf-mem-protect-case, 0_tftf-mem-protect-sentinel, 0_tftf-power-cycle-0, 0_tftf-power-cycle-1, 0_tftf-resume-after-mem-protect, 0_tftf-resume-after-warm-reset, 0_tftf-tests-crashed-zero, 0_tftf-tests-failed-zero, 0_tftf-tests-passed, 0_tftf-warm-reset-case, 0_tftf-warm-reset-sentinel-modified, tftf-boot-banner, tftf-exit, tftf-mem-protect-case, tftf-mem-protect-sentinel, tftf-power-cycle-0, tftf-power-cycle-1, tftf-resume-after-mem-protect, tftf-resume-after-warm-reset, tftf-tests-crashed-zero, tftf-tests-failed-zero, tftf-tests-passed, tftf-warm-reset-case, tftf-warm-reset-sentinel-modified | |||||||
n1sdp2 observed devices, Boot | |||||||
int_1, lava | |||||||
TFTF, tftf | · | · | |||||
Chromebook | |||||||
mt8192-asurada-rev13 observed devices, Boot | |||||||
int_1, int_2, lava | |||||||
mt8195-cherry-tomato-r23 observed devices, Boot | |||||||
int_1, int_2, lava | |||||||
mt8186-corsola-tentacruel3 observed devices, Boot | |||||||
int_1, int_2, lava | |||||||
mt8188-geralt3 observed devices, Boot | |||||||
int_1, int_2, lava | |||||||
mt8196-rauru-navi4 observed devices, Boot | |||||||
int_1, int_2, lava | · | · | · | ||||
sc7180-trogdor-lazor-limozeen4 observed devices, Boot | |||||||
int_1, int_2, lava | |||||||
Raspberry Pi | |||||||
bcm2837-rpi-3-b-322 observed devices, Boot | |||||||
int_1, lava | · | · | · | · | |||
STMicroelectronics | |||||||
stm32mp15x-eval3 observed devices, Boot | |||||||
int_1, lava | · |
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.