[BUG] Captured dependency paths make bootstrap artifacts nondeterministic #63
Labels
No labels
alpha-1
bug
ci
docs
duplicate
enhancement
help wanted
invalid
performance
phase-6
question
refactor
security
wontfix
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
erix/rootd#63
Loading…
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?
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
b48c798b48e0dbae351d565262807fbe3626fdeawith 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
.rodatachanged LLVM symbol suffixes; the string-table size and aligned ELF layout changed as well.Environment and identity
b48c798b48e0dbae351d565262807fbe3626fdea, productionrootd-runtime-release-imagefeature.602a09a43e774aba7c78caec83b912ba2c733c803f6dc185d556b50fc7674841.x86_64-unknown-nonetarget.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.