Error on Windows calling cargo: "no such command: `+bisector-nightly-2024-03-01-x86_64-pc-windows-msvc`"

[MingweiSamuel]

Not sure exactly what is going on, but bisect-rustc is instantly finding that every single version is regressed, even though some aren't. Using --prompt showed some more info, it seems it's somehow not calling cargo +toolchain correctly.

Console output:

$ cargo bisect-rustc --start=2024-03-01 --end=2024-03-19 --prompt
checking the start range to find a passing nightly
installing nightly-2024-03-01
rust-std-nightly-x86_64-pc-windows-msvc: 20.03 MB / 20.03 MB [============================================================================================================================================] 100.00 % 10.58 MB/s testing...
error: no such command: `+bisector-nightly-2024-03-01-x86_64-pc-windows-msvc`

        Cargo does not handle `+toolchain` directives.
        Did you mean to invoke `cargo` through `rustup` instead?

nightly-2024-03-01 finished with exit code Some(101).
please select an action to take:
> mark regressed
  mark baseline
  retry

Calling cargo directly seems to work as expected:

$ cargo +nightly-2024-03-01-x86_64-pc-windows-msvc test
   Compiling indexmap v2.1.0
   Compiling winnow v0.5.30
   Compiling syn v2.0.42
   ...

cargo -Vv

$ cargo -Vv
cargo 1.79.0-nightly (28e7b2bc0 2024-04-05)
release: 1.79.0-nightly
commit-hash: 28e7b2bc0a812f90126be30f48a00a4ada990eaa
commit-date: 2024-04-05
host: x86_64-pc-windows-msvc
libgit2: 1.7.2 (sys:0.18.3 vendored)
libcurl: 8.6.0-DEV (sys:0.4.72+curl-8.6.0 vendored ssl:Schannel)
os: Windows 10.0.19045 (Windows 10 Home) [64-bit]

$ cargo bisect-rustc --version
cargo-bisect-rustc-bisect-rustc 0.6.8

[MingweiSamuel]

Does not happen on my apple-darwin mac

[ehuss]

Thanks for the report! I believe you should be able to fix this by either:

• Setting the environment variable RUSTUP_WINDOWS_PATH_ADD_BIN=0
• Using a - in the filename, like cargo-bisect-rustc

This should be fixed after the next release of rustup.

Closing as I believe this is a duplicate of #244. If that doesn't solve your issue, feel free to reopen.

[MingweiSamuel]

Yup worked, thanks!