Eric Huss

Update on this: This can be fixed by setting the environment variable `RUSTUP_WINDOWS_PATH_ADD_BIN=0`. We hope to change the default option for that in rustup in the future.

This should now be fixed by default with rustup 1.27.1 released today.

It should be working. Can you share your exact `.cargo/config.toml` file? Is your `.cargo/config.toml` in the project directory where you are running `cargo-bisect-rustc`? What is the output of `cargo-bisect-rustc -vv...

The reason you are seeing different behavior when running manually is because you are not passing the `--target` flag. When you don't pass the `--target` flag, rustflags are passed to...

BTW, if you need to pass rustflags to proc-macros even when `--target` is used, you can do something like this: ```toml [target.'x86_64-unknown-linux-gnu'] rustflags="-Clink-arg=-Wl,--no-undefined-version" [host] rustflags="-Clink-arg=-Wl,--no-undefined-version" ``` And pass the `-Zhost-config...

I think at least documenting it would be good. One place I forgot to mention this is in https://rust-lang.github.io/cargo-bisect-rustc/usage.html#scripting, where it should be mentioned that scripts don't need to specify...

> However, that does lead me to this question: Is there any verbosity level at which cargo bisect rustc will print out the contextual parameters it is setting I don't...

Unfortunately I don't have any ideas on what could be the problem. The error is generated when the SHA256 checksum of the file downloaded over the network does not match...

It's a bit complicated, but without `-p` or `--manifest-path`, it looks for the first `Cargo.toml` starting in the current directory and walks upwards. It can be a little complicated with...

Thanks! Can you also add a link to the attribute from the [built-in attribute list](https://github.com/rust-lang/reference/blob/master/src/attributes.md#built-in-attributes-index)?