-
Notifications
You must be signed in to change notification settings - Fork 93
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
bazel coverage not working for 0.0.9 #219
Comments
@c-mita for triage |
@c-mita friendly ping |
I can't even build the example in this repo with Bazel 6.0.0 or later... Regardless, I suspect the issue is here:
The "coverage" feature is a duplicate of the "gcc_coverage_map_format" one, but the latter "requires" the former and there's a conflict since they provide the same "profile" symbol. |
I got that issue too on Debian 12 with GCC 12. If you enable rool_cc toolchain coverage fails (because symbol
Running |
Description of the problem / feature request:
Bazel Coverage failing with rules_cc 0.0.9
Feature requests: what underlying problem are you trying to solve with this feature?
We're trying to uprev our rules_cc from ancient 0.0.1 to latest version as we prepare to migrate to bazel 7.0.0
Bugs: what's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
test.cpp
BUILD
What operating system are you running Bazel on?
ubuntu 20.04
What's the output of
bazel info release
?release 6.3.2
What version of rules_cc do you use? Can you paste the workspace rule used to fetch rules_cc? What other relevant dependencies does your project have?
0.0.9
What Bazel options do you use to trigger the issue? What C++ toolchain do you use?
I ran this with bazel 6.3.2 in the rules cc example section by adding the following section above. I'm using the cc toolchain configured by rules_cc.
System gcc is 9.0.0
Have you found anything relevant by searching the web?
https://groups.google.com/d/topic/bazel-discuss/dtduJBlb-nw (doesn't seem relevant)
Any other information, logs, or outputs that you want to share?
The text was updated successfully, but these errors were encountered: