rust-lang / rust-lang/rustc-perf
Create benchmark for long running but eventually unsuccessful compile
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 732
- Forks
- 189
- Avg merge
- 10h 52m
- Merged PRs (30d)
- 43
Description
Currently there is a compiler test for https://github.com/rust-lang/rust/issues/65131 in rust-lang/rust, but the test suite for the compiler has no way of testing long running yet unsuccessful compiles. This is more of a job for the rustc-perf tool. The issue is that rustc-perf does not have the ability to measure how long failed compiles take which would be necessary for this test to be successfully moved to this repo.
Contributor guide
No contributing guide indexed for this repository
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 with the existing compiler test in src/test/ui/issues/issue-65131.rs and then inspect rustc-perf's benchmark measurement flow. Identify where unsuccessful compiles are recorded or discarded; done means rustc-perf can measure their duration so this long-running failure test can be moved into the repository.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- performance
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100