Tracking issue for better testing for dist artifacts
Open
Nobody has claimed this yet.
A-testsuite
C-tracking-issue
T-bootstrap
T-compiler
T-infra
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.1k
- PR merge metrics
- PR metrics pending
Description
This is a tracking issue for improving the testing for dist artifacts (including but not limited to, dist compilers and dist components like rustc-src).
As of the time of writing, much of dist components are not really tested or exercised in a basic way (modulo tests through opt-dist, but not all dist artifacts go through opt-dist).
Example regressions
- #136795
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 reading the tracking issue and the existing opt-dist testing path, then identify which dist artifacts, including dist compilers and rustc-src, are not exercised. Done means adding basic coverage for the relevant artifacts and preventing regressions like #136795.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system, release, testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100