wasm driver: rust-src on the build host drifts wasm-lock.json — remap the sysroot src #128
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Found on a linux/x86_64 dev host (first non-CI host of the lock's host class):
./gradlew buildfailed verifyWasmDriverLock with a byte-different (still correct) binary despite the pinned toolchain (1.97.1, byte-identical rustc) and the pinned wasm-bindgen 0.2.127 release binary. Cause: with the rust-src component installed (rust-analyzer installs it), rustc resolves std sources to the local sysroot path instead of the precompiled std's /rustc/ virtual path; std panic locations then embed the longer local path (+624 bytes). Fix: cargoBuildWasm appends --remap-path-prefix=/lib/rustlib/src/rust=/rustc/ at execution time — inert where rust-src is absent (CI reproduces the same locked hash, verified in a debian container). D61's per-host-class reproducibility assumption holds again. D61 addendum in the same change-set.