Repository navigation
"build-script-build contains outdated or invalid JSON" #4855
Description
Something is going wrong with miri in nightly-2026-02-12.
# Cargo.toml
[package]
name = "repro"
edition = "2024"
publish = false// build.rs
fn main() {}// src/main.rs
fn main() {}$ cargo clean && cargo +nightly-2026-02-12 miri run
Compiling repro v0.0.0
error: failed to run custom build command for `repro v0.0.0`
Caused by:
process didn't exit successfully: `$RUSTUP_HOME/toolchains/nightly-2026-02-12-x86_64-unknown-linux-gnu/bin/cargo-miri runner target/miri/debug/build/repro-e8018e58e4b6ef17/build-script-build` (exit status: 1)
--- stderr
fatal error: file "target/miri/debug/build/repro-e8018e58e4b6ef17/build-script-build" contains outdated or invalid JSON; try `cargo clean`
Activity
Pr0methean commentedon Feb 12, 2026
The breakage happened tonight some time between 16:55 and 19:06 UTC-8.
RalfJung commentedon Feb 12, 2026
Probably caused by rust-lang/rust#152240.
Hopefully fixed by rust-lang/cargo#16631.
fix: apply `host.runner` only when `host-config` enabled
ci(miri): pin nightly to 2026-02-11 (#19314)
ci: pin nightly toolchain to fix Miri breakage
fix: Fix Miri CI failure by cleaning stale Miri artifacts before test…
Pr0methean commentedon Feb 12, 2026
Is there any way we can have the affected build "yanked", or a new one released ahead of schedule, so that we don't have to temporarily pin the version, rebase all open PRs against that change, and then revert it?
RalfJung commentedon Feb 17, 2026
Fixed by rust-lang/cargo#16631.
There's no way to yank a Rust nightly release, nor any way to make a new nightly ahead of schedule, as far as I know.
chore: Unpin Miri nightly toolchain (#1900)
chore: unpin miri toolchain
fix: Fix Miri CI failure by cleaning stale Miri artifacts before test…
chore: Unpin Miri nightly toolchain (delta-io#1900)
fix: Fix Miri CI failure by cleaning stale Miri artifacts before test…
chore: Unpin Miri nightly toolchain (delta-io#1900)