fix: pin turbo to 2.9.14 to avoid random Windows CI crashes#11351
Merged
Conversation
turbo 2.10.1+ ships libghostty-vt compiled with non-baseline CPU instructions, causing STATUS_ILLEGAL_INSTRUCTION (0xC000001D) hard crashes on some Windows CI runners. The crash is deterministic per-CPU but appears random across heterogeneous runner pools, showing up as 'turbo build' exiting 1 with no task output. Revert the catalog pin from 2.10.5 back to 2.9.14 (last version this repo ran cleanly on Windows). Revisit once a fully-fixed stable (>=2.10.6) is verified on Windows. Ref: vercel/turborepo#13346
timotheeguerin
marked this pull request as ready for review
July 22, 2026 15:18
timotheeguerin
requested review from
bterlson,
catalinaperalta,
iscai-msft,
markcowl and
witemple-msft
as code owners
July 22, 2026 15:18
timotheeguerin
enabled auto-merge
July 22, 2026 15:18
iscai-msft
approved these changes
Jul 22, 2026
Contributor
|
No changes needing a change description found. |
|
You can try these changes here
|
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
2 participants
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
turbo buildrandomly fails on Windows CI, exiting with code 1 and no task output / no "run failed" summary:```
$ turbo --filter=!@typespec/monorepo "build"
• Packages in scope: ...
• Running build in 65 packages
• Remote caching disabled
[ELIFECYCLE] Command failed with exit code 1.
```
Root cause
The failures started when turbo was bumped `2.9.14 → 2.10.5` in #11265.
This is vercel/turborepo#13346: turbo 2.10.1+ ships a vendored `libghostty-vt` compiled with non-baseline CPU instructions (inherited from the release build runners). On CPUs lacking those instructions, turbo crashes with `STATUS_ILLEGAL_INSTRUCTION (0xC000001D)` — a hard process kill, so turbo never prints its own error summary.
The crash is deterministic per-CPU but appears random because CI runner pools have heterogeneous CPUs — you only fail when scheduled onto an older/leaner microarchitecture.
The upstream fix (vercel/turborepo#13352) only rebuilt `libghostty-vt` and was verified on a single maintainer VM; no fully-fixed stable (`>=2.10.6`) exists yet.
Fix
Revert the catalog pin to `turbo: 2.9.14` — the version this repo ran on Windows CI cleanly for ~7 weeks (Jun 2 → Jul 21). Added a comment pointing to the upstream issue so the next dependency bump can gate re-upgrade on a verified fixed stable.
The `pnpm-lock.yaml` change was applied surgically (only the 7 turbo entries) to avoid the registry-proxy tarball churn that `pnpm install --lockfile-only` introduces; validated with `pnpm install --frozen-lockfile`.