Skip to content

CI: stop and retry zig cc when it hangs under ARM64 emulation - #1105

Merged
KnifeLemon merged 1 commit into
mainfrom
ci/zig-cc-timeout
Nov 4, 2026
Merged

KnifeLemon merged 1 commit into
mainfrom
ci/zig-cc-timeout

Conversation

@KnifeLemon

Copy link
Copy Markdown
Owner

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

  • `build/build-explorer-menu.ps1` runs `zig cc` with an 8-minute limit per try and 3 tries. A try that runs over is stopped (with its child processes) and the next one uses a cache of its own. Compile errors still fail at once.
  • In `ci.yml`, both Explorer menu steps get `timeout-minutes: 30`, so a hang can no longer take the whole job.

Tested

  • x64 and arm64 builds locally: DLL and MSIX written as before.
  • The retry loop on its own with a process that sleeps past the limit: it stops it, tries 3 times, then fails with a clear message.

🤖 Generated with Claude Code

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>
@github-actions github-actions Bot added the build Build and release label Nov 4, 2026
@KnifeLemon
KnifeLemon merged commit e66490a into main Nov 4, 2026
12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

build Build and release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant