rust-lang / rust-lang/rustc-perf
triage oddity: why did same PR show up in two consecutive weeks
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 733
- Forks
- 189
- Avg merge
- 10h 52m
- Merged PRs (30d)
- 43
Description
2023-05-23 triage used this url: https://perf.rust-lang.org/?start=3ea9ad532474343426e564b997891e459cda89a6&end=cda5becc27cbc7106646fbc40aacea5e7896d954&absolute=false&stat=instructions%3Au
2023-05-30 triage used this url: https://perf.rust-lang.org/?start=cda5becc27cbc7106646fbc40aacea5e7896d954&end=1221e43bdf413f7c405e9b17ef19d76c88222098&absolute=false&stat=instructions%3Au
why did PR https://github.com/rust-lang/rust/pull/111807 show up in both triage runs? The end of the first is equal to the start of the second, so one would think that would imply that the PR would fall into at most one of the two ranges, not both.
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 by reproducing the two perf.rust-lang.org URLs from the issue and tracing how their start and end revisions select changes. Check why rust-lang/rust pull request 111807 appears in both ranges. Done means documenting the boundary behavior or identifying the correction needed so consecutive triage ranges do not overlap unexpectedly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- performance
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100