Dextroid17 dd5c052dc5 ci: fail when a test executable is built that no test runs ...

A test executable can be declared with add_test_executable and never
registered with add_test. It is then built and never run, and ctest
reports a full pass over what it knows, so nothing in CI says so.

Measured on main, five test executables are in this state: the driver's
mesh and recorder tests, the guest formatting tests, the video out flip
tests and the BDA device tests.

tools/check_test_registration.py compares the test executables CMake
builds, read from the build graph, against the add_test calls in the
generated CTestTestfile.cmake files, which are written at configure time
and so do not depend on the build having finished. It fails on a test
executable that nothing runs, and records those five by name so the job
stays green until they are dealt with.

Both jobs run it right after configure, before anything is built.

2026-10-08 11:40:34 +02:00

..

area-labels.yml

ci: label pull requests by area

2026-09-28 15:50:48 +02:00

build.yml

ci: fail when a test executable is built that no test runs

2026-10-08 11:40:34 +02:00

conflict-label.yml

ci: label pull requests that conflict with main

2026-09-28 15:50:48 +02:00

conventions.yml

ci: check pull requests against the contributing rules

2026-10-07 17:03:37 +02:00

labels.yml

ci(labels): set colors only for some

2026-09-30 19:15:51 +03:00

pr-overlap.yml

ci: comment on pull requests that overlap other open pull requests

2026-09-29 16:24:47 +02:00

progress-comment.yml

feat(tools): report progress changes on pull requests

2026-09-27 18:47:32 +02:00

progress-report.yml

feat(tools): report progress changes on pull requests

2026-09-27 18:47:32 +02:00

progress.yml

feat(tools): add progress map for system libraries and shader instructions

2026-09-27 18:21:34 +02:00

release.yml

fix(ci): use git bash for windows release

2026-09-29 00:38:21 +03:00