Taiki Endo

> Do environment variables need to be set on the physical machine to run the program? Whether the environment variable set here is the same as the docker internal, using...

@Ekleog-NEAR One of the problems is that you are passing the output of --export-prefix to GITHUB_ENV; -export-prefix adds a prefix for the UNIX shell, which is not the format GITHUB_ENV...

> Would you be interested in a PR that showcases the more "advanced" (multiple codecov labels, using with python tests that call into rust, etc.) use cases of cargo-llvm-cov in...

> Is there a way to check if the current version of `rustc` supports MCDC? I think you can check rustc version like: https://github.com/taiki-e/cargo-llvm-cov/blob/550dc19643ac31cd4fd5dac52e9d3239a1295ea9/src/main.rs#L205-L211

The actual error here is due to the version of llvm-cov command (-show-mcdc requires LLVM 18+), so a check like `cmd!(&cx.llvm_cov, "show", "--help").read()?.contains("-show-mcdc")` might be better.

Published in 0.6.11. Thanks @aytey!

See https://github.com/crossbeam-rs/crossbeam/pull/1039.

What is the actual error you received? The location of the compiled binaries can be obtained via the CARGO_BIN_EXE_ environment variable, but IIUC assert_cmd refers to that environment variable, so...

> So dev-dependencies should be merged with dependencies under dependencies in the bin crate? Yes, but dev-dependencies should win, similar to the way dev-dependencies are handled in normal tests, because...

I would accept a PR to improve docs. (It would be better to add it before or after [the section on VSCode](https://github.com/taiki-e/cargo-llvm-cov?tab=readme-ov-file#display-coverage-in-vs-code).) It would not be so easy to add...