Skip to content

ci(fuzz): pin the fuzz-smoke nightly toolchain (ICE workaround) - #378

Merged
kingchenc merged 1 commit into
mainfrom
fix/fuzz-pin-nightly
Jul 26, 2026
Merged

ci(fuzz): pin the fuzz-smoke nightly toolchain (ICE workaround)#378
kingchenc merged 1 commit into
mainfrom
fix/fuzz-pin-nightly

Conversation

@kingchenc

Copy link
Copy Markdown
Collaborator

The Fuzz (smoke) job started failing with a rustc codegen ICE (rustc_codegen_ssa/src/mir/operand.rs) while building tokio on the rolling nightly — an upstream compiler bug, not our code. Pin the fuzz toolchain to a fixed nightly (nightly-2026-07-01, pre-ICE and compatible with the pinned cargo-fuzz) so CI is deterministic. Bump the date deliberately when a newer nightly is needed. Config-only; no code change.

The rolling `nightly` regressed with a rustc codegen ICE
(rustc_codegen_ssa/src/mir/operand.rs) while building tokio in the fuzz-smoke
job — an upstream compiler bug unrelated to our code. Pin the fuzz toolchain to
a fixed, ICE-free nightly for deterministic CI; bump the date deliberately.
@kingchenc
kingchenc merged commit 29891eb into main Jul 26, 2026
@kingchenc
kingchenc deleted the fix/fuzz-pin-nightly branch July 26, 2026 16:01
@codecov

codecov Bot commented Jul 26, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

kingchenc added a commit that referenced this pull request Jul 27, 2026
…#386)

#378 pinned the fuzz-smoke toolchain INSTALL to nightly-2026-07-01, but the five
`cargo fuzz run` commands still invoked `cargo +nightly` — which resolves to
the rolling nightly, ignoring the pin. That rolling nightly carries the
rustc_codegen_ssa ICE building tokio, so Fuzz (smoke) kept failing on main.
Point each command at `+nightly-2026-07-01` so it uses the pinned, ICE-free
toolchain that the install step actually provides.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant