compiletest: Add a variant of `{{build-base}}` that points to the current test's build subdirectory
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.1k
- PR merge metrics
- PR metrics pending
Description
Several of the existing tests that use {{build-base}} would be better off using a test-specific output subdirectory (or an automatically-cleared scratch directory), rather than the “root” output directory shared by all tests in a test suite.
Unfortunately, this is currently hard to accomplish because parse_name_value_directive doesn't have access to any test-specific data structures, only the &Config shared by all tests in the suite.
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 tracing compiletest's parse_name_value_directive and the shared Config it currently receives. Determine how a directive variant can identify the current test's build subdirectory or an automatically-cleared scratch directory, then verify that tests using it no longer share the suite's root output directory.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100