compiletest: pin or restrict supported external dependency versions
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.1k
- PR merge metrics
- PR metrics pending
Description
To the best of my knowledge, test suites supported by compiletest currently rely on external dependencies in e.g. ui or run-make test suites but we do not have any sanity checks on their versions or even the specific external dependency used. For example, which C/C++ compilers are picked for a given environment usually calls out to something like the cc crate, but we don't otherwise pin them down. This makes reproducing the tests locally very challenging or near impossible. Or for Python, I don't think we sanity check which Python versions are "supported" by the test suites.
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 examining compiletest's ui and run-make test suites and how the cc crate selects C/C++ compilers. Identify how Python and compiler versions are currently discovered, then define checks or restrictions that make supported external dependency versions explicit and test reproduction more reliable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, cpp, python, rust
- Domain
- build-system, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100