Eric Huss

> The difference is whether the variables are available at runtime, which as far as I can tell they aren't. Can you say more about why it does not appear...

Ah, I see. `CARGO_BIN_EXE` is only set at build time. It does say "only set when building", but I imagine that could be made clearer somehow. Maybe that and `OUT_DIR`...

What are your gitignore rules?

Ah, I see what is happening. Git reports the entire directory as untracked if there is at least one non-ignored file. Cargo [walks the entire directory](https://github.com/rust-lang/cargo/blob/3b142db791ac023a8e8e856c1b18c1ea9367a81a/src/cargo/sources/path.rs#L326) without further consulting git....

I think it would probably be fine to make the above addition of `recurse_untracked_dirs`, and fix the `target` check so that it only matches a directory named `target` in the...

This sounds like there are multiple issues here, can we maybe separate it out into separate things? For running without cargo, [running without cargo](https://rust-lang.github.io/cargo-bisect-rustc/examples/without-cargo.html) explains what you need to do....

I think that between #103 and #237, this is resolved. However, there is an issue with github access that causes it to panic. I have opened #318 to fix that.

My guess would be that there is an issue with the PATH environment variable. `cargo-bisect-rustc` just executes the command "cargo" from your PATH (although the lookup rules on windows is...

Can you show which version of rustup you have and what your PATH looks like? I suspect it is https://github.com/rust-lang/rustup/issues/3036, and it may be an issue with PATH.

Yea, the issue is https://github.com/rust-lang/rustup/issues/3036. I have posted a fix there for it.