Pin Windows Native job to windows-2022 runner#1918
Closed
gastaldi wants to merge 1 commit into
Closed
Conversation
The windows-latest runner now resolves to windows-2025-vs2026, which ships Visual Studio 2026. graalvm/setup-graalvm@v1 only knows about VS 2017/2019/2022 installation paths when searching for vcvarsall.bat, causing the Windows Native job to fail.
Contributor
Author
|
Closing — this repo already has |
|
Following jobs contain at least one flaky test:
Run summary: https://github.com/quarkus-qe/quarkus-test-framework/actions/runs/27541279765?pr=1918 Flaky tests:
Failure stacktrace |
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
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.
Summary
windows-latesttowindows-2022indaily.yamlWhy
The
windows-latestGitHub Actions runner now resolves towindows-2025-vs2026(rolled out June 8–15, 2026), which ships with Visual Studio 2026. Thegraalvm/setup-graalvm@v1action only knows about VS 2017, 2019, and 2022 installation paths when searching forvcvarsall.bat, so it fails immediately with:Reported upstream as graalvm/setup-graalvm#218, fix submitted in graalvm/setup-graalvm#219.
Why only
daily.yamlWindows Nativedaily.yamlWindows Native — usesgraalvm/setup-graalvm@v1which needsvcvarsall.bat→ pinned towindows-2022daily.yamlWindows JVM (line 163) — does not use GraalVM/native-image, sowindows-latestis finepr.yamlWindows JVM (line 129) — same, no GraalVM involvedOnce
graalvm/setup-graalvmadds VS2026 support, this can be reverted back towindows-latest.Test plan
windows-2022runner