Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Coverage when spawning target/{profile}/{bin_name} in llvm-cov nextest --workspace? #321

Open
KSXGitHub opened this issue Oct 14, 2023 · 2 comments
Labels
C-question Category: A question S-needs-repro Status: This issue has no reproduction and needs a reproduction to make progress.

Comments

@KSXGitHub
Copy link

KSXGitHub commented Oct 14, 2023

I have integration tests that invoke the binary to test it comprehensively. It would be nice if coverage can be collected from the binary too.

Before opening this issue ticket, I have tested it by inspecting std::env::var("RUSTFLAGS") in build.rs but an Err was returned.

@taiki-e
Copy link
Owner

taiki-e commented Oct 15, 2023

Binaries are supported, but coverage is not collected if the process is killed without completing (#235, limitation of LLVM/rustc.)

If it does not work, please provide a reproduction of the problem.

@taiki-e taiki-e added the C-question Category: A question label Oct 15, 2023
@taiki-e
Copy link
Owner

taiki-e commented Oct 22, 2023

Before opening this issue ticket, I have tested it by inspecting std::env::var("RUSTFLAGS") in build.rs but an Err was returned.

Since Rust 1.55, Cargo does not pass the RUSTFLAGS environment variable to the build script. CARGO_ENCODED_RUSTFLAGS is passed instead. (rust-lang/cargo#9601)

@taiki-e taiki-e added needs-mcve Call for participation: This issue needs a Minimal Complete and Verifiable Example S-needs-repro Status: This issue has no reproduction and needs a reproduction to make progress. and removed needs-mcve Call for participation: This issue needs a Minimal Complete and Verifiable Example labels Apr 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-question Category: A question S-needs-repro Status: This issue has no reproduction and needs a reproduction to make progress.
Projects
None yet
Development

No branches or pull requests

2 participants