CI: pin Windows CUDA build to windows-2022#243
Merged
garyo merged 2 commits intoJun 15, 2026
Conversation
The windows-latest runner image now ships Visual Studio 2026, whose host compiler is rejected by CUDA 12.4's nvcc (only VS 2017-2022 are supported), breaking CMake's CUDA compiler detection at configure time. Pin the CUDA Windows build to windows-2022 until the toolchain catches up. The non-CUDA Windows job stays on windows-latest. Signed-off-by: Gary Oberbrunner <[email protected]>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
The Windows
<config=Release>(CUDA) CI job started failing on all PRs and pushes. It dies at CMake configure time during CUDA compiler detection, before any source is compiled:GitHub rolled the
windows-latestrunner image forward to Visual Studio 2026 (log paths showVisual Studio\18\Enterprise). The pinned CUDA 12.4.1 toolkit'snvcconly accepts host compilers VS 2017–2022, so it rejects the newcl.exe.This is purely runner-image drift — no source change triggered it (the last
mainbuild was green; the non-CUDA Windows job, which doesn't invokenvcc, still passes).Fix
Pin the CUDA Windows matrix entry to
windows-2022, which still provides VS 2022. The non-CUDA Windows job stays onwindows-latestso we keep coverage of the newer toolchain.This is a stopgap until a CUDA toolkit that supports VS 2026 can be adopted on Windows.