Repository navigation
CI: stop and retry zig cc when it hangs under ARM64 emulation - #1105
Merged
Merged
Conversation
The win-arm64 job hung at "Build Explorer menu extension" twice on 2026-11-04 (#1090, #1101) until the two-hour limit, while the same step takes about two minutes. zig cc now gets eight minutes per try, three tries, each retry with a cache of its own; the step itself stops after 30 minutes. Co-Authored-By: Claude Opus 5.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
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.
Why
`build (win-arm64)` hung at Build Explorer menu extension twice today (#1090 and #1101) until the two-hour job limit. The same step normally takes about two minutes there. The log stops right after `build FileeExplorerMenu.dll 2.3.0 (arm64)`, so it is `zig cc`, which runs under x64 emulation on the ARM runner.
What changes
Tested
🤖 Generated with Claude Code