[BUG] Captured dependency paths make bootstrap artifacts nondeterministic #63

Closed
opened 2026-11-13 05:02:50 +01:00 by erikinkinen · 0 comments
Owner

Summary

The exact bootstrap artifact gate can fail for unchanged source and compiler because captured dependency filenames change the linked ELF. A successful rerun does not establish reproducibility.

Reproduction

Build Rootd b48c798b48e0dbae351d565262807fbe3626fdea with Rust 1.93.1 from independent captured workspaces, replaying the same retained source snapshot. Use the production release feature and the existing owned Cargo gateway. Compare the complete ELFs and their section tables, rather than only repeating the scalar check.

Expected and actual behavior

Identical declared inputs should produce identical artifacts. The retained source snapshot and all eleven Cargo metadata values matched, but actual linked outputs were 271,760 and 271,768 bytes. Dependency filenames in .rodata changed LLVM symbol suffixes; the string-table size and aligned ELF layout changed as well.

Environment and identity

  • Rootd: b48c798b48e0dbae351d565262807fbe3626fdea, production rootd-runtime-release-image feature.
  • Source snapshot SHA256: 602a09a43e774aba7c78caec83b912ba2c733c803f6dc185d556b50fc7674841.
  • Toolchain: Rust 1.93.1, x86-64 Linux host, x86_64-unknown-none target.
  • No image or runtime authority change is involved; this is a native build defect.

Evidence and prior checks

CI 1761 passed the old exact gate, while another build of the same inputs failed it. Independent retained artifact pairs reproduce the difference. Mapping the complete captured source operation across all crates produced two byte-identical 271,768-byte ELFs, SHA256 e9ba9c1c354d5b59f64f4b747b4c6bc1ce16d52ac9b28beeb838ffa163e64413. All semantic inventory fields and compiler identity remained equal to the original baseline.

Tracking

Related: #1 and #20. The corrective scope is Rootd's owned production and semantic artifact boundaries. Shared Cargo producers and image builders still need a coordinated policy before whole-system or self-hosting reproducibility can be claimed.

  • Reproduce with actual independent artifacts and the same frozen inputs.
  • Apply one all-crate path policy to both artifact boundaries.
  • Pass the original gates with fresh complete-artifact regression coverage.
## Summary The exact bootstrap artifact gate can fail for unchanged source and compiler because captured dependency filenames change the linked ELF. A successful rerun does not establish reproducibility. ## Reproduction Build Rootd `b48c798b48e0dbae351d565262807fbe3626fdea` with Rust 1.93.1 from independent captured workspaces, replaying the same retained source snapshot. Use the production release feature and the existing owned Cargo gateway. Compare the complete ELFs and their section tables, rather than only repeating the scalar check. ## Expected and actual behavior Identical declared inputs should produce identical artifacts. The retained source snapshot and all eleven Cargo metadata values matched, but actual linked outputs were 271,760 and 271,768 bytes. Dependency filenames in `.rodata` changed LLVM symbol suffixes; the string-table size and aligned ELF layout changed as well. ## Environment and identity - Rootd: `b48c798b48e0dbae351d565262807fbe3626fdea`, production `rootd-runtime-release-image` feature. - Source snapshot SHA256: `602a09a43e774aba7c78caec83b912ba2c733c803f6dc185d556b50fc7674841`. - Toolchain: Rust 1.93.1, x86-64 Linux host, `x86_64-unknown-none` target. - No image or runtime authority change is involved; this is a native build defect. ## Evidence and prior checks [CI 1761](https://git.erikinkinen.fi/erix/rootd/actions/runs/1761) passed the old exact gate, while another build of the same inputs failed it. Independent retained artifact pairs reproduce the difference. Mapping the complete captured source operation across all crates produced two byte-identical 271,768-byte ELFs, SHA256 `e9ba9c1c354d5b59f64f4b747b4c6bc1ce16d52ac9b28beeb838ffa163e64413`. All semantic inventory fields and compiler identity remained equal to the original baseline. ## Tracking Related: #1 and #20. The corrective scope is Rootd's owned production and semantic artifact boundaries. Shared Cargo producers and image builders still need a coordinated policy before whole-system or self-hosting reproducibility can be claimed. - [x] Reproduce with actual independent artifacts and the same frozen inputs. - [x] Apply one all-crate path policy to both artifact boundaries. - [x] Pass the original gates with fresh complete-artifact regression coverage.
erikinkinen added this to the Alpha 1 milestone 2026-11-13 05:02:50 +01:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
erix/rootd#63
No description provided.