rustdoc reproducibility issue due to nondeterministic anon.llvm.<hash>
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.2k
- PR merge metrics
- PR metrics pending
Description
I am facing a reproducibility issue with rustdoc in Yocto project. The issue is happening due to a different llvm.<hash> generation between the builds.
What could be the reason for this llvm.<hash> is nondeterministic. Any optimization settings causing this? (I tried the PGO enabling/disabling but has no effect).
[Info] - This issue we've seen in past https://internals.rust-lang.org/t/rustdoc-binary-is-not-reproducible/20027. There we concluded the issue is fixed by disabling PGO and setting tools = ["rust-demangler",] but it is not fixed. Somehow with those settings rustdoc is not generating at all. (We found that by removing tools = ["rust-demangler",] the rustdoc is generated)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with a reproducible Yocto build of rustdoc, comparing the generated anon.llvm. values while varying PGO and tools = ["rust-demangler",]. No file or test is named; done means identifying the source of the differing hash and documenting or fixing settings so repeated builds produce the same rustdoc.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100