CNA-VGAP-026: The Windows renderer families have no automatic native Windows execution: DIRECTX9 has no CI job, the DIRECTX11/12, DIRECT2D and GDI lanes are manual, and Direct2D's release gate is blocked

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 Direct3D and GDI Windows workflows run only on manual dispatch, no workflow selects DIRECTX9, GDI tests are not registered in cross builds, DXGI device removal is only simulated, and the Direct2D release gate is blocked.

Identifier
CNA-VGAP-026
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
DIRECTX9, DIRECTX11, DIRECTX12, DIRECT2D and GDI renderer identities on native Windows

Expected behaviour

Renderers whose home platform is Windows need at least one automatic native run.

Actual behaviour at TARGET

d3d-windows-ci.yml (matrix DIRECTX11, DIRECTX12, DIRECT2D) and gdi-windows-ci.yml trigger only on workflow_dispatch; no workflow selects DIRECTX9. CMakeLists.txt registers GDI CTests only if(NOT CMAKE_CROSSCOMPILING), so the Linux cross/Wine route runs none. Device removal on the DXGI renderers is exercised only through debug simulation hooks. direct2d-release-gate.md keeps criteria 4 and 5 BLOCKED until docs/direct2d-native-evidence.md and docs/direct2d-physical-presentation-evidence.md exist; neither does at 009d40f5. The Wine/DXVK/vkd3d cross-build lanes are local evidence, not native Windows.

Source locations

Evidence

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

Independently reported as CNA-VGAP-043 (folded into this entry by the adversarial audit): The automatic win32-cross job builds and runs only the standalone Win32 platform harness under Wine; every engine-level Windows workflow is manual, and GDI's examples skip CTest registration when cross-compiling.

Focused reproduction

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

Current tests

Cross-built parity fixtures run under Wine locally; the manual workflows exist but have no schedule or push trigger.

Regression test

Push or scheduled triggers for the Windows lanes, a DIRECTX9 job, and the two recorded Direct2D evidence runs.

Blast radius

All Windows-native rendering, presentation (including PresentInterval pacing and tearing), DPI and device-loss behaviour.

Workaround

No workaround is known.

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

Deep dives
Direct3D evidence: native Windows · Windows 2D renderers: Direct2D tests
Known issues
Verification gap index