fix(ci): install python3 so svd_check_* tests register on CI #41

Merged

hoogv merged 0 commits from refs/pull/41/head into dev

2026-07-22 13:19:33 +00:00

hoogv commented

2026-07-22 13:03:38 +00:00

(Migrated from codeberg.org)

Description

Installs python3 in tests.yml's dependency-install step so the svd_check_* tests actually register and run on CI, instead of CTest silently finding zero tests.

Why

Change justification per ISO 9001 section 7.5.2: tests.yml's dependency-install step only installed nodejs and cmake, not python3. The svd_check_* tests are gated on find_package(Python3 COMPONENTS Interpreter), so on the real CI runner they silently never registered, and combined with the TI mmWave SDK also being absent, CTest ended up with zero registered tests — the CI job was building successfully but validating nothing.

Closes #40

Type of Change

Bug fix / nonconformity resolution

Impact Assessment

Functional impact: None — CI-only fix, no product/driver code changes.
Regulatory impact: None.
QMS impact: None.
Risk impact: No — existing risk coverage sufficient.

Testing

CI pipeline passes (compile, unit tests, integration tests, static analysis)
Manually tested: configured with -DTI_MMWAVE_SDK_PATH=/nonexistent (simulating the real runner's environment), confirmed Python3 is found, all 6 svd_check_* tests register and pass, and ti_hal_comparison skips gracefully with its existing STATUS message rather than erroring.
No regressions observed in related areas

PR Size

S (10–50 lines)

Checklist

Commit messages follow type(scope): description convention with Relates to #<issue> footer
PR template filled in completely
No unverified external binaries introduced (see QMS-GITFLOW-001 Binary Security section)
All commits leave the codebase in a compilable, passing-tests state (Commit Integrity Rule)

Summary

Added python3 to the install step. Left the TI SDK gap alone — ti_hal_comparison gracefully skips when the SDK isn't found, by design, so that's expected behavior rather than a bug to fix here.

## Description Installs `python3` in `tests.yml`'s dependency-install step so the `svd_check_*` tests actually register and run on CI, instead of CTest silently finding zero tests. ## Why Change justification per ISO 9001 section 7.5.2: `tests.yml`'s dependency-install step only installed `nodejs` and `cmake`, not `python3`. The `svd_check_*` tests are gated on `find_package(Python3 COMPONENTS Interpreter)`, so on the real CI runner they silently never registered, and combined with the TI mmWave SDK also being absent, CTest ended up with zero registered tests — the CI job was building successfully but validating nothing. ## Related Issue Closes #40 ## Type of Change - [x] Bug fix / nonconformity resolution ## Impact Assessment - **Functional impact:** None — CI-only fix, no product/driver code changes. - **Regulatory impact:** None. - **QMS impact:** None. - **Risk impact:** No — existing risk coverage sufficient. ## Testing - [x] CI pipeline passes (compile, unit tests, integration tests, static analysis) - [x] Manually tested: configured with `-DTI_MMWAVE_SDK_PATH=/nonexistent` (simulating the real runner's environment), confirmed Python3 is found, all 6 `svd_check_*` tests register and pass, and `ti_hal_comparison` skips gracefully with its existing STATUS message rather than erroring. - [x] No regressions observed in related areas ## PR Size - [x] S (10–50 lines) ## Checklist - [x] Commit messages follow `type(scope): description` convention with `Relates to #<issue>` footer - [x] PR template filled in completely - [x] No unverified external binaries introduced (see QMS-GITFLOW-001 Binary Security section) - [x] All commits leave the codebase in a compilable, passing-tests state (Commit Integrity Rule) ## Summary Added `python3` to the install step. Left the TI SDK gap alone — `ti_hal_comparison` gracefully skips when the SDK isn't found, by design, so that's expected behavior rather than a bug to fix here.

hoogv added the

Rows
Columns