tools of artifacts are not tested
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.1k
- PR merge metrics
- PR metrics pending
Description
Sometimes tools break in that x.py test $tool passes but the x.py dist artifacts of that tool can no longer find all libs: https://github.com/rust-lang/rust/issues/137469 https://github.com/rust-lang/rust/issues/145201
suggestion:
After building the dist artifacts in ci, actually install those artifacts, remove the build dir and then run each tool against a pub fn main() {}.rs , at least rustc, rustc + cranelift, rustfmt, clippy, miri, rustdoc and make sure this passes
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 the CI flow that builds the dist artifacts and the x.py entry points for rustc, rustc with Cranelift, rustfmt, clippy, miri, and rustdoc. Install the artifacts, remove the build directory, then run each tool against a minimal Rust program. Done means CI verifies every listed tool can find its libraries after installation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- ci-cd, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100