cargo-bisect-rustc
cargo-bisect-rustc copied to clipboard
rust-lang
Bisects rustc, either nightlies or CI artifacts
``` $ cargo-bisect-rustc --preserve --start=e67f09ac799e4a6e4e90147d62c94c9ddcc94197 --end=7aa361390867181d225a7775340f50e8162e16a2 bisecting ci builds starting at e67f09ac799e4a6e4e90147d62c94c9ddcc94197, ending at 7aa361390867181d225a7775340f50e8162e16a2 opening existing repository at "rust.git" Found origin remote under name `origin` refreshing repository at "rust.git"...
if you pass an invalid `--component`, cbr will print a rather unhelpful message ````rust Err(InstallError::NotFound { .. }) => { // go back just one day, presumably missing a nightly...
This should avoid having to patch ahash and similar crates to not do nightly feature detection and break the bisection (see https://github.com/rust-lang/rust/issues/123276#issuecomment-2075001510 for an example). We could also do this...
I have a script like ``` #!/bin/sh ! rustc /tmp/crash.rs |& grep -Ii "query stack" ``` which returns 1 or 0 depending on whether rustc says "query stack" while processing...
It can be helpful if the full command that is being executed is displayed, which can help with debugging issues (such as #284). I would recommend showing the command with...
when working with `--access checkout`, it seems like cbr still sends api calls to github in order to figure out the commits contained in a rollup instead of using the...
1) run CBR with --preserve and do a bisection. 2) now do the same bisection but with `--component rls` for example => cbr will NOT notice that it lacks the...
When I use `--start 2023-01-01` but the ice I am bisecting has not hit nightly yet, CBR will just quit with "latest nightly cant reproduce the regression" It would be...
This adds a workflow to publish cargo-bisect-rustc to crates.io from CI.
When bisecting issues it often happens that a regression was introduced long enough ago that CI artifacts are unavailable, and we only have a list of PRs between two nightlies...
