Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tracking Issue for Reproducible Build bugs and challenges #129080

Open
62 of 81 tasks
jieyouxu opened this issue Aug 14, 2024 · 0 comments
Open
62 of 81 tasks

Tracking Issue for Reproducible Build bugs and challenges #129080

jieyouxu opened this issue Aug 14, 2024 · 0 comments
Labels
A-debuginfo Area: Debugging information in compiled programs (DWARF, PDB, etc.) A-diagnostics Area: Messages for errors, warnings, and lints A-reproducibility Area: Reproducible / deterministic builds C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC D-diagnostic-infra Diagnostics: Issues that affect all diagnostics, or relate to the diagnostic machinery itself. S-tracking-forever Status: Never to be closed. T-bootstrap Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap) T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-infra Relevant to the infrastructure team, which will review and decide on the PR/issue.

Comments

@jieyouxu
Copy link
Member

jieyouxu commented Aug 14, 2024

This is a tracking issue for collecting and triaging bugs and challenges that hinder our ability to produce reproducible and deterministic builds.

This tracking issue is used as a hub for connecting to other relevant issues, e.g., bugs or open design questions. This tracking issue is however not meant for large scale discussion, questions, or bug reports about a feature. Instead, open a dedicated issue for the specific matter and add the A-reproducibility Area: Reproducible / deterministic builds label, and tag with OS/architecture/target labels as suitable.

This tracking issue is unlikely to be exhaustive. Please add suitable entries and edit as new issues and PRs pop up or if old issues and PRs are rediscovered.

Copy pastas for the inline labels

A-debuginfo Area: Debugging information in compiled programs (DWARF, PDB, etc.)
A-diagnostics Area: Messages for errors, warnings, and lints
A-LLVM Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues.
A-reproducibility Area: Reproducible / deterministic builds
A-run-make Area: port run-make Makefiles to rmake.rs
A-testsuite Area: The testsuite used to check the correctness of rustc
C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC
F-trim-paths Feature: trim-paths
T-bootstrap Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)
T-cargo Relevant to the cargo team, which will review and decide on the PR/issue.
T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
T-lang Relevant to the language team, which will review and decide on the PR/issue.
T-libs Relevant to the library team, which will review and decide on the PR/issue.
T-libs-api Relevant to the library API team, which will review and decide on the PR/issue.
T-infra Relevant to the infrastructure team, which will review and decide on the PR/issue.
T-rustdoc Relevant to the rustdoc team, which will review and decide on the PR/issue.
O-wasm Target: WASM (WebAssembly), http://webassembly.org/
O-windows Operating system: Windows
O-windows-msvc Toolchain: MSVC, Operating system: Windows
O-windows-gnu Toolchain: GNU, Operating system: Windows
O-macos Operating system: macOS
O-apple Operating system: Apple (macOS, iOS, tvOS, visionOS, watchOS)
O-AArch64 Armv8-A or later processors in AArch64 mode
O-x86_64 Target: x86-64 processors (like x86_64-*)

Bugs and issues

Tracking/meta issues:

Resolved:

Related issues, RFCs, MCPs and discussions

Related PRs

@jieyouxu jieyouxu added T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-bootstrap Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap) T-infra Relevant to the infrastructure team, which will review and decide on the PR/issue. C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC A-reproducibility Area: Reproducible / deterministic builds T-dev-tools Relevant to the dev-tools subteam, which will review and decide on the PR/issue. E-hard Call for participation: Hard difficulty. Experience needed to fix: A lot. labels Aug 14, 2024
@Dylan-DPC Dylan-DPC added S-tracking-forever Status: Never to be closed. and removed E-hard Call for participation: Hard difficulty. Experience needed to fix: A lot. labels Aug 14, 2024
@jieyouxu jieyouxu added A-diagnostics Area: Messages for errors, warnings, and lints D-diagnostic-infra Diagnostics: Issues that affect all diagnostics, or relate to the diagnostic machinery itself. labels Aug 14, 2024
@rust-lang rust-lang locked as too heated and limited conversation to collaborators Aug 14, 2024
@jieyouxu jieyouxu added A-debuginfo Area: Debugging information in compiled programs (DWARF, PDB, etc.) and removed T-dev-tools Relevant to the dev-tools subteam, which will review and decide on the PR/issue. labels Aug 15, 2024
@rust-lang rust-lang unlocked this conversation Aug 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-debuginfo Area: Debugging information in compiled programs (DWARF, PDB, etc.) A-diagnostics Area: Messages for errors, warnings, and lints A-reproducibility Area: Reproducible / deterministic builds C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC D-diagnostic-infra Diagnostics: Issues that affect all diagnostics, or relate to the diagnostic machinery itself. S-tracking-forever Status: Never to be closed. T-bootstrap Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap) T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-infra Relevant to the infrastructure team, which will review and decide on the PR/issue.
Projects
None yet
Development

No branches or pull requests

2 participants