Dist tools should receive some degree of smoke tests
Open
Nobody has claimed this yet.
A-testsuite
C-enhancement
T-bootstrap
T-compiler
T-infra
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.1k
- PR merge metrics
- PR metrics pending
Description
We should exercise the dist rustfmt, rust-analyzer, rustdoc, cargo etc. tools shipped as part of a dist toolchain in at least a basic manner. E.g.
- That the tools have reasonable version info.
- Links against the right libraries.
- Smoke test against a basic hello world input doesn't immediately explode.
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 by locating how the dist toolchain packages rustfmt, rust-analyzer, rustdoc, and cargo. Run each tool with basic version checks and a hello-world input, then inspect whether it links against the expected libraries. Done means the shipped tools have smoke coverage and fail visibly when version, linkage, or basic execution is broken.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system, release, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100