Board test coverage
Which boards in TF CI were seen testing which firmware branch, and with what result. Test results for the last 7 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-M
TF-M boards by branch and suite, last 7 days, all ci runs.
main | release | Unattributed | |
|---|---|---|---|
Arm | |||
musca-b9 observed devices, 105.7 assertions | |||
NS_SYSTEM_BOOTING | · | ||
mcuboot_suite | · | ||
non_secure_regression_suite | · | ||
psa_api_suite | · | · | |
secure_regression_suite | · | ||
NXP | |||
frdmmcxn9473 observed devices, 156.0 assertions | |||
non_secure_regression_suite | · | ||
secure_regression_suite | · | ||
lpcxpresso55s693 observed devices, 136.5 assertions | |||
NS_SYSTEM_BOOTING | · | ||
non_secure_regression_suite | · | ||
secure_regression_suite | · | ||
STMicroelectronics | |||
b-u585i-iot02a3 observed devices, 194.5 assertions | |||
non_secure_regression_suite | · | ||
secure_regression_suite | · | ||
stm32h573i-dk3 observed devices, 194.5 assertions | |||
non_secure_regression_suite | · | ||
secure_regression_suite | · | ||
stm32u3c5zi-q3 observed devices | |||
non_secure_regression_suite | · | · | |
secure_regression_suite | · | · | |
stm32wba65i-dk14 observed devices, 196.9 assertions | |||
non_secure_regression_suite | · | ||
secure_regression_suite | · | ||
Other boards | |||
nucleo-u3c5zi-q3 observed devices, 198.0 assertions | |||
non_secure_regression_suite | · | · | |
secure_regression_suite | · | · |
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-M
- CI attempts per month
- Complete attempts, %
Test-case detail: September 2026 to October 2026.