CI: pin Windows jobs to windows-2025 (VS2026 MSVC ICE)#62
Merged
Conversation
windows-latest now resolves to windows-2025-vs2026; its VS 18 compiler intermittently crashes (CL.exe 0xE06D7363) generating code for plutovg in the lunasvg dependency. Pin release + ci-engine Windows jobs to the known-good VS 2022 image. ci-guava-mcp is swift-build only, unaffected. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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
Release run 27360741493 failed in Editor Windows → Build native dependencies:
GitHub is redirecting
windows-latestto the newwindows-2025-vs2026image (NOTICE in the run log). Its VS 18 MSVC intermittently crashes with an internal compiler error while generating code for plutovg (bundled with lunasvg v3.5.0). It is nondeterministic — a ci-engine run on the same image passed an hour earlier. macOS (clang) is unaffected.Fix
Pin the two jobs that compile the native deps with MSVC to
windows-2025(VS 2022, the image everything was green on before the redirect):release.yml→ Editor Windowsci-engine.yml→ Windows matrix entryci-guava-mcp.ymlstays onwindows-latest— it only runsswift buildand never invokes CL.exe.Once merged, re-dispatch the Release workflow from
main. The earlier June 4 failures (Package step--target→--product, bootstrap encoding) were already fixed in 5e8af2b and are included in the tag.🤖 Generated with Claude Code