cargo-bisect-rustc
cargo-bisect-rustc copied to clipboard
Add options to skip verifying bisection ranges
Closes #258
Adds two options for bypassing verifying the start and end of nightly and CI ranges. If no start nightly has been provided, the start date will be detected as usual.
What's this feature doing? speeding up bisection by ignoring the start/end so you only run things in between the start/end?
Yeah, if you know for sure that a regression happened between (for example) stable and beta, you can save some time by skipping checking those
Hmm... that needs a bit more documentation on the flags. To me it sounded like verifying that the commit/nightly exists or somehow is valid in itself. But this is solely about not running the bisection on the start/end and only running it between the given values
Also: why do we have different flags for CI artifacts and nightly?
I'll update the help to document this better. I made two flags so that we don't skip verifying the CI range if the user has only provided nightly dates. It would probably make more sense to have it be a single flag that skips verifying whichever of the two the user has provided.