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

C++ Coverage not working with --test_env="LCOV_MERGER=/bin/true" #22969

Open
Ryang20718 opened this issue Jul 8, 2024 · 2 comments
Open

C++ Coverage not working with --test_env="LCOV_MERGER=/bin/true" #22969

Ryang20718 opened this issue Jul 8, 2024 · 2 comments
Labels
coverage P4 This is either out of scope or we don't have bandwidth to review a PR. (No assignee) team-Rules-CPP Issues for C++ rules type: bug

Comments

@Ryang20718
Copy link

Description of the bug:

C++ Code coverage doesn't work with this flag set

Which category does this issue belong to?

C++ Rules

What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.

add a cc_library and a cc_test, use bazel coverage --combined_report=lcov --instrument_test_targets --instrumentation_filter="//" --test_env="LCOV_MERGER=/bin/true"

To see that coverage isn't getting generated

Which operating system are you running Bazel on?

20.04

What is the output of bazel info release?

6.5.0

If bazel info release returns development version or (@non-git), tell us how you built Bazel.

No response

What's the output of git remote get-url origin; git rev-parse HEAD ?

No response

If this is a regression, please try to identify the Bazel commit where the bug was introduced with bazelisk --bisect.

No response

Have you found anything relevant by searching the web?

No response

Any other information, logs, or outputs that you want to share?

Removing --test_env="LCOV_MERGER=/bin/true" yields coverage results

@comius
Copy link
Contributor

comius commented Jul 10, 2024

cc @c-mita for triage

@c-mita
Copy link
Member

c-mita commented Jul 10, 2024

What's the expectation here?

That coverage works when you appear to be overriding the tool it needs to work?

@c-mita c-mita added P4 This is either out of scope or we don't have bandwidth to review a PR. (No assignee) and removed untriaged labels Jul 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
coverage P4 This is either out of scope or we don't have bandwidth to review a PR. (No assignee) team-Rules-CPP Issues for C++ rules type: bug
Projects
None yet
Development

No branches or pull requests

6 participants