windows.yml currently builds AND runs offscreen_png on windows-2022. The build/link is a legitimate hermetic gate (proves the Vulkan SDK generates SPIR-V on a clean checkout, no hidden Linux->Windows dep). But the RUN step calls Context::new() -> needs a VkDevice, and hosted windows-2022 runners have no Vulkan ICD, so the run will likely fail even when the build succeeds.
Proposed:
- Keep on hosted
windows-2022: checkout + Vulkan SDK + ClangCL + premake beta7 + scripts\win.cmd build --release (BUILD/LINK ONLY, no run). This is the provenance + hermeticity gate.
- Move the actual offscreen render + PNG artifact to the self-hosted GPU runner (see the self-hosted-runner issue), or a Windows self-hosted box with the NVIDIA driver.
Also: windows.yml has never run on a real runner — first push will need tuning of jakoch/install-vulkan-sdk-action version, the VS ClangCL component IDs, and choco install make. Track those fixes here.
windows.ymlcurrently builds AND runsoffscreen_pngonwindows-2022. The build/link is a legitimate hermetic gate (proves the Vulkan SDK generates SPIR-V on a clean checkout, no hidden Linux->Windows dep). But the RUN step callsContext::new()-> needs a VkDevice, and hosted windows-2022 runners have no Vulkan ICD, so the run will likely fail even when the build succeeds.Proposed:
windows-2022: checkout + Vulkan SDK + ClangCL + premake beta7 +scripts\win.cmd build --release(BUILD/LINK ONLY, no run). This is the provenance + hermeticity gate.Also: windows.yml has never run on a real runner — first push will need tuning of
jakoch/install-vulkan-sdk-actionversion, the VS ClangCL component IDs, andchoco install make. Track those fixes here.