Skip to content

ci(fuzz): run cargo-fuzz with the pinned nightly, not the rolling one - #386

Merged
kingchenc merged 1 commit into
mainfrom
fix/fuzz-use-pinned-nightly
Jul 27, 2026
Merged

ci(fuzz): run cargo-fuzz with the pinned nightly, not the rolling one#386
kingchenc merged 1 commit into
mainfrom
fix/fuzz-use-pinned-nightly

Conversation

@kingchenc

Copy link
Copy Markdown
Collaborator

#378 pinned the fuzz-smoke toolchain install to nightly-2026-07-01, but the five cargo fuzz run commands still called cargo +nightly — which resolves to the rolling nightly and ignores the pin. The rolling nightly carries the rustc_codegen_ssa/operand.rs ICE building tokio, so Fuzz (smoke) stayed red on main. Change each command to cargo +nightly-2026-07-01 fuzz … so it uses the pinned, ICE-free toolchain the install step provides. (Verified in the failing log: the crashing rustc was toolchains/nightly-…, not nightly-2026-07-01-….)

#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.
@codecov

codecov Bot commented Jul 27, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@kingchenc
kingchenc merged commit 42e22fa into main Jul 27, 2026
56 checks passed
@kingchenc
kingchenc deleted the fix/fuzz-use-pinned-nightly branch July 27, 2026 07:45
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