-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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 work in ubuntu 22.04 #20993
Labels
coverage
P2
We'll consider working on this in future. (Assignee optional)
team-Rules-API
API for writing rules/aspects: providers, runfiles, actions, artifacts
type: bug
Comments
sgowroji
added
the
team-Configurability
platforms, toolchains, cquery, select(), config transitions
label
Jan 23, 2024
gregestren
added
team-Rules-API
API for writing rules/aspects: providers, runfiles, actions, artifacts
and removed
team-Configurability
platforms, toolchains, cquery, select(), config transitions
labels
Jan 31, 2024
@c-mita for triage |
@c-mita friendly ping |
c-mita
added
P2
We'll consider working on this in future. (Assignee optional)
and removed
untriaged
labels
Feb 21, 2024
What compiler version are you using? |
GCC 13.2 |
Since the fault is coming from gcov and I don't have a reproduction, there's not much I can really suggest. At least on my workstation, I can perform C++ coverage with bazel 6.4.0 and GCC 13.2... Do |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
coverage
P2
We'll consider working on this in future. (Assignee optional)
team-Rules-API
API for writing rules/aspects: providers, runfiles, actions, artifacts
type: bug
Description of the bug:
After running bazel coverage --combined_report=lcov target I get this segmentation fault
external/bazel_tools/tools/test/collect_cc_coverage.sh: line 113: 181 Segmentation fault (core dumped) "${GCOV}" -i$COVERAGE_GCOV_OPTIONS -o "$ (dirname ${gcda})" "${gcda}"
cat: '.gcov': No such file or directory
rm: cannot remove '.gcov': No such file or directory
Which category does this issue belong to?
No response
What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
bazel coverage --combined_report=lcov target
Which operating system are you running Bazel on?
ubuntu 22.04
What is the output of
bazel info release
?release 6.4.0
If
bazel info release
returnsdevelopment 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 master; git rev-parse HEAD
?No response
Is this a regression? If yes, please try to identify the Bazel commit where the bug was introduced.
No response
Have you found anything relevant by searching the web?
#18874
Any other information, logs, or outputs that you want to share?
No response
The text was updated successfully, but these errors were encountered: