rust-lang / rust-lang/cargo-bisect-rustc
prefer using toolchains already installed
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 206
- Forks
- 60
- PR merge metrics
- No merged PRs in 30d
Description
Let's say we would naturally try to bisect a change between the 1st and the 30th of a month, the bisect might go something like this:
check 30th
check 1st
check 15th
check 7th
check 11th
check 9th
check 10th <- regression
For each of these steps we might have to download a new nightly.
Now, if we already have, from a previous bisection, nightlies of the 14th, 6th, 11th and 8th installed, I believe we could just use these to already limit our search space so that the total number of nightlies we have to download is reduced to "between 8th and 11th"?
Should save a bunch of bandwith and time.
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 at the bisection workflow and trace how nightly toolchains are selected and downloaded. Investigate how already-installed nightlies could constrain the search interval; done means bisection reuses those toolchains and avoids downloading nightlies outside the remaining range.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100