CNA-VGAP-027: No workflow runs the roughly eighty SDL_Renderer_* renderer CTests, and they are not registered on Windows or Emscripten

CNA snapshot 009d40f5  ·  Known Issues › Verification gaps  ·  source links pinned to 009d40f5

✓

Evidence basis: source-verified at the pinned commit; tests exist (not executed for this page). Claims on this page were checked by reading the CNA source at commit 009d40f5; unless a sentence says otherwise, nothing here was built or executed. Nothing on this page was executed unless the Evidence section says so.

The SDL_RENDERER example tests are registered only when NOT EMSCRIPTEN AND NOT WIN32; input-ci.yml builds SDL_RENDERER but runs ctest -L input, and apple-ci.yml runs CnaTests directly.

Identifier
CNA-VGAP-027
Category
Verification gap
Subsystem
Testing & evidence
Status
Open
Verified against
CNA 009d40f5 (009d40f5dd085c4e674d3479675fac84b12b3e0a)
Evidence basis
Source-verified: read at TARGET, not executed
Tests touching this area
Yes: see Current tests
Affected contract
SDL_RENDERER renderer identity (its SDL_Renderer_* CTests)

Expected behaviour

SDL_RENDERER is a portable default renderer (its home includes Windows); its renderer tests should run somewhere automatically.

Actual behaviour at TARGET

CMakeLists.txt registers 80 SDL_Renderer_* tests under if(CNA_BUILD_TESTS AND NOT EMSCRIPTEN AND NOT WIN32 ...). input-ci.yml configures SDL_RENDERER and runs ctest -L input; apple-ci.yml configures SDL_RENDERER on macOS and runs the CnaTests binary directly. No job runs the renderer suite.

Source locations

Evidence

Checked by reading the named sources at 009d40f5; nothing was built or executed for this entry.

Focused reproduction

No focused reproduction is known. Nothing has been invented here; the evidence above is what exists.

Current tests

As above.

Regression test

A CI job that runs ctest -R ^SDL_Renderer_ under Xvfb, and registrations for Windows builds.

Blast radius

All SDL_RENDERER drawing, clears, presentation and readback; CNA-BUG-205 is an example of drift that a run would expose.

Workaround

No workaround is known.

The same subject is explained at several altitudes. These are the neighbouring pages at each one.