rust-lang / rust-lang/rustc-perf
Adjust definition of “mixed” perf run result
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 732
- Forks
- 189
- Avg merge
- 10h 52m
- Merged PRs (30d)
- 43
Description
The definition of a “mixed” perf run result is pretty poor. If there is any positive results whatsoever, even if vastly outweighed by negative results, it’s considered mixed. We should change that. Here’s an example of such a case.
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
Open the linked perf comparison to understand the reported imbalance between positive and negative results. Trace where rustc-perf classifies a run as “mixed,” then clarify the intended rule with maintainers before changing it. Done means the example is no longer classified as mixed under the agreed definition and related classification behavior is covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- performance
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100