TF test results
Synced 18:19 UTC, 12 h ago stale

Data as of 28 Oct 2026, 18:19 UTC

Last LAVA sync
28 Oct 2026, 18:19 UTC
Last Jenkins sync
28 Oct 2026, 18:32 UTC
Last S3 export sync
7 Oct 2026, 09:53 UTC
Open fetch errors
6,509
About the data
Owner: NXP Clear filters
  1. Boards
  2. NXP

2 boards ran 70 evaluations in the last 30 days. 0 first attempts failed; 0 passed on retry. No evaluation failed after retries.

Evaluations

70

70 attempts, 0 cancelled

Completion

100.0%

of 70 attempts

Evaluated pass rate 100.0% of 70 evaluations with a verdict

Failed after retries

0 of 70

0 failed first time, 0 passed on retry

Changes with a failed boot on these boards

0 of 0

Allow-CI+2 for TF-A; linked TF-M runs. Counts are change, patchset and board pairs. 0 with no boot verdict.

Linked to a change: 0.0% of 70 evaluations

The bench

One tape per board: evaluations per day, stacked by final outcome. Each tape has its own scale, topped by its busiest day, so compare boards by the totals beside their names. Failures sit on top as caps.

  1. FRDMMCXN947 NXP 33

    No failures

  2. No failures

29 Sep 202628 Oct 2026
Test-case detail: 29 Sep 2026 to 28 Oct 2026. 0 days without data.
Show the bench as a table
FRDMMCXN947 33 3300000
LPCXpresso55S69 37 3700000

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.

FRDMMCXN947 0 0 0 0.0% of 33
LPCXpresso55S69 0 0 0 0.0% of 37

Failed after retries

CI evaluations with a final code, lab or unclassified failure, newest first; 0 of 0 shown. Health checks and manual runs are never listed here.

Attempts
No evaluation failed after retries in this window.

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.

5 devices across 2 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.

BoardDevicesHealth checks passedPass rateStatus
FRDMMCXN947 3 21 of 21 100.0% All passed
LPCXpresso55S69 2 14 of 14 100.0% All passed