STM32H573I-DK

Status
Live
3 units live.
SoC and family
STM32H573I, STMicroelectronics
Device type
stm32h573i-dk
Activity
First seen 1 Oct 2025, last seen 28 Oct 2026.
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
Evaluations
4,7804,804 attempts, 31 cancelled
Completion
99.2%of 4,773 attemptsComplete out of complete and incomplete attempts. Cancelled attempts are listed, never counted.
Evaluated pass rate
100.0%of 480 evaluations with a verdictFinal attempts that passed, out of pass and code. Lab 3, cancelled 31 and unclassified 11 are shown, never folded in.
Failed after retries
14 of 4,78028 failed first time, 13 passed on retry
Changes with a failed boot on this board
n/aNot available for this range: change lineage exists for the live window only.

Last 12 months

Evaluations per week, stacked by final outcome.

Job level only: 27 Oct 2025 to 27 Feb 2026No data held: 28 Feb 2026 to 28 Feb 2026Job level only: 1 Mar 2026 to 6 Sep 2026Test-case detail: 7 Sep 2026 to 30 Sep 2026Test-case detail: 1 Oct 2026 to 29 Oct 2026
Job-level history: 27 Oct 2025 to 6 Sep 2026. Test-case detail: 7 Sep 2026 to 29 Oct 2026. 1 day without data.
  • No data held: 28 Feb 2026 to 28 Feb 2026

History by month

Before the live window we know whether each attempt completed and how retries ended, not why it failed or which change it was. Months with no data held are listed under the chart.

  • Evaluations per month
  • Incomplete attempts, % of attempts
  • Failed after retries, % of evaluations
Incidents marked: Lab 17 Sep.
Test-case detail: September 2026 to October 2026.
Job level only: 1 Oct 2025 to 27 Feb 2026No data held: 28 Feb 2026 to 28 Feb 2026Job level only: 1 Mar 2026 to 6 Sep 2026Test-case detail: 7 Sep 2026 to 30 Sep 2026Test-case detail: 1 Oct 2026 to 29 Oct 2026
Job-level history: 1 Oct 2025 to 6 Sep 2026. Test-case detail: 7 Sep 2026 to 29 Oct 2026. 1 day without data.
  • No data held: 28 Feb 2026 to 28 Feb 2026

Units

CI attempts per physical unit, retries included. Passing on another unit can help identify a unit fault. Health checks are fleet health.

Unit
Attempts
First-attempt failures
Passed on another unit
Passed on the same unit
Last health check
stm32h573i-dk-01
1,545
10
2
2
Complete 28 Oct 14:04
stm32h573i-dk-02
1,561
9
5
0
Complete 28 Oct 13:30
stm32h573i-dk-03
1,667
9
4
0
Complete 28 Oct 23:44

Evaluations

One row per builder build on this board, newest first, with every attempt. CI runs only; 7 of 7 shown.

When
Build
Change
Branch
Attempts
Verdict
28 Apr 08:56
tf-m-build-config 532519
not recorded
Branch not recorded
  1. 03
Unclassified
26 Nov 13:03
tf-m-build-config 305493
not recorded
Branch not recorded
  1. 01
  2. 03
Lab
infra s3
25 Nov 09:35
tf-m-build-config 301651
not recorded
Branch not recorded
  1. 03
  2. 03
Unclassified
24 Nov 20:30
tf-m-build-config 300548
not recorded
Branch not recorded
  1. 01
  2. 03
Unclassified
24 Nov 18:18
tf-m-build-config 300404
not recorded
Branch not recorded
  1. 03
  2. 01
Unclassified
24 Nov 16:36
tf-m-build-config 299731
not recorded
Branch not recorded
  1. 03
  2. 02
Unclassified
7 Nov 22:26
tf-m-build-config 269398
not recorded
Branch not recorded
  1. 03
  2. 02
Unclassified

Fleet health

Health checks, not CI results. They never count towards any rate on this page.

0 of 18 health checks failed in the last 7 days.
All passed
Showing the latest 18 checks.
One tick per health check, oldest to newest. Each opens its job.PassedFailedCancelled

Incidents

  1. Lab 17 Sep 2026 to 18 Sep 2026

    LAVA logger DNS failures