Skip to content

Pin Windows Native job to windows-2022 runner#1918

Closed
gastaldi wants to merge 1 commit into
mainfrom
fix-windows-native-runner
Closed

Pin Windows Native job to windows-2022 runner#1918
gastaldi wants to merge 1 commit into
mainfrom
fix-windows-native-runner

Conversation

@gastaldi

Copy link
Copy Markdown
Contributor

Summary

  • Pin the Windows Native job runner from windows-latest to windows-2022 in daily.yaml

Why

The windows-latest GitHub Actions runner now resolves to windows-2025-vs2026 (rolled out June 8–15, 2026), which ships with Visual Studio 2026. The graalvm/setup-graalvm@v1 action only knows about VS 2017, 2019, and 2022 installation paths when searching for vcvarsall.bat, so it fails immediately with:

##[error]Failed to find vcvarsall.bat

Reported upstream as graalvm/setup-graalvm#218, fix submitted in graalvm/setup-graalvm#219.

Why only daily.yaml Windows Native

  • daily.yaml Windows Native — uses graalvm/setup-graalvm@v1 which needs vcvarsall.batpinned to windows-2022
  • daily.yaml Windows JVM (line 163) — does not use GraalVM/native-image, so windows-latest is fine
  • pr.yaml Windows JVM (line 129) — same, no GraalVM involved

Once graalvm/setup-graalvm adds VS2026 support, this can be reverted back to windows-latest.

Test plan

  • Verify the Windows Native daily build passes with the windows-2022 runner

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.
@gastaldi
gastaldi requested a review from rsvoboda June 15, 2026 10:52
@gastaldi

Copy link
Copy Markdown
Contributor Author

Closing — this repo already has distribution: mandrel in the setup-graalvm step, so the vcvarsall.bat lookup is skipped and this fix is not needed.

@gastaldi gastaldi closed this Jun 15, 2026
@gastaldi
gastaldi deleted the fix-windows-native-runner branch June 15, 2026 10:59
@github-actions

Copy link
Copy Markdown

Following jobs contain at least one flaky test:

  • Linux JVM

Run summary: https://github.com/quarkus-qe/quarkus-test-framework/actions/runs/27541279765?pr=1918

Flaky tests:


io.quarkus.qe.RemoteDevModeGreetingResourceIT.shouldLoadResources

  • Failure message: Condition with Lambda expression in io.quarkus.test.bootstrap.BaseService was not fulfilled within 5 minutes.
  • Failed in jobs:
    • Linux JVM
Failure stacktrace
org.awaitility.core.ConditionTimeoutException: Condition with Lambda expression in io.quarkus.test.bootstrap.BaseService was not fulfilled within 5 minutes.
	at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:167)
	at org.awaitility.core.CallableCondition.await(CallableCondition.java:78)
	at org.awaitility.core.CallableCondition.await(CallableCondition.java:26)
	at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:1160)
	at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:1129)
	at io.quarkus.test.utils.AwaitilityUtils.untilIsTrue(AwaitilityUtils.java:99)
	at io.quarkus.test.bootstrap.BaseService.waitUntilServiceIsStarted(BaseService.java:410)
	at io.quarkus.test.bootstrap.BaseService.start(BaseService.java:279)
	at io.quarkus.test.bootstrap.RestService.start(RestService.java:187)
	at io.quarkus.test.bootstrap.QuarkusScenarioBootstrap.lambda$beforeEach$6(QuarkusScenarioBootstrap.java:116)
	at java.base/java.util.ArrayList.forEach(ArrayList.java:1596)
	at io.quarkus.test.bootstrap.QuarkusScenarioBootstrap.beforeEach(QuarkusScenarioBootstrap.java:114)
	at io.quarkus.test.bootstrap.QuarkusScenarioBootstrap.beforeEach(QuarkusScenarioBootstrap.java:108)
	at java.base/java.util.ArrayList.forEach(ArrayList.java:1596)
	at java.base/java.util.ArrayList.forEach(ArrayList.java:1596)


Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant