fix(ci): tests.yml missing python3 causes "No tests were found" #40

New issue

Closed

opened 2026-07-22 13:01:20 +00:00 by hoogv · 0 comments

hoogv commented

2026-07-22 13:01:20 +00:00

(Migrated from codeberg.org)

Description

.forgejo/workflows/tests.yml's "Install build dependencies" step only installs nodejs and cmake, not python3. testing/CMakeLists.txt's svd_check_* tests are gated on find_package(Python3 COMPONENTS Interpreter), so on the actual CI runner they silently don't get registered:

-- Could NOT find Python3 (missing: Python3_EXECUTABLE Interpreter)
-- hal_awr6843 tests: no Python3 interpreter found -- skipping svd_check_adcbuf
-- hal_awr6843 tests: no local TI mmWave SDK found (checked TI_MMWAVE_SDK_PATH and known default install locations) -- skipping ti_hal_comparison
...
No tests were found!!!

Since the TI mmWave SDK also isn't present on this runner (a separate, likely-unavoidable gap -- it's proprietary and not vendored in this repo, per testing/CMakeLists.txt's own comment), both test families end up skipped simultaneously, leaving CTest with zero registered tests -- the CI job currently validates nothing.

Scope

Install python3 in tests.yml's dependency-install step, so the svd_check_* tests (pure open-source Python tooling, no licensing concern) actually register and run on CI
Confirm the resulting CI run registers and passes the svd_check_* tests

Functional Impact

None -- CI-only fix, no product/driver code changes.

Regulatory Impact

None

QMS Impact

None

Risk Impact

No -- existing risk coverage sufficient.

Relates to #16, #38

### Description `.forgejo/workflows/tests.yml`'s "Install build dependencies" step only installs `nodejs` and `cmake`, not `python3`. `testing/CMakeLists.txt`'s `svd_check_*` tests are gated on `find_package(Python3 COMPONENTS Interpreter)`, so on the actual CI runner they silently don't get registered: ``` -- Could NOT find Python3 (missing: Python3_EXECUTABLE Interpreter) -- hal_awr6843 tests: no Python3 interpreter found -- skipping svd_check_adcbuf -- hal_awr6843 tests: no local TI mmWave SDK found (checked TI_MMWAVE_SDK_PATH and known default install locations) -- skipping ti_hal_comparison ... No tests were found!!! ``` Since the TI mmWave SDK also isn't present on this runner (a separate, likely-unavoidable gap -- it's proprietary and not vendored in this repo, per `testing/CMakeLists.txt`'s own comment), both test families end up skipped simultaneously, leaving CTest with zero registered tests -- the CI job currently validates nothing. ### Scope - [x] Install `python3` in `tests.yml`'s dependency-install step, so the `svd_check_*` tests (pure open-source Python tooling, no licensing concern) actually register and run on CI - [x] Confirm the resulting CI run registers and passes the `svd_check_*` tests ### Functional Impact None -- CI-only fix, no product/driver code changes. ### Regulatory Impact None ### QMS Impact None ### Risk Impact No -- existing risk coverage sufficient. ### Related Issues / PRs Relates to #16, #38

hoogv self-assigned this

2026-07-23 12:02:02 +00:00

hoogv added this to the Development project

2026-07-23 12:02:05 +00:00

hoogv added the

Rows
Columns