compiletest: add self-instrumentation for time taken between different steps
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.1k
- PR merge metrics
- PR metrics pending
Description
E.g. for PRs like #136404, it would be very useful to have self-instrumentation for the time taken between steps (e.g. test discovery/collection, directive parsing, etc.). The compiler has self-instrumentation infra that we can steal adapt for our purposes.
Marked as E-hard because it can be annoying to implement this cleanly in the current code structure (there is no phase-split between discovery -> directive parsing -> test running).
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 discovery/collection, directive-parsing, and test-running flow, then compare it with the compiler's existing self-instrumentation infrastructure. Done means compiletest reports the time taken between those steps, despite the current lack of a phase split.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100