We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
tools/bazel coverage //...--cache_test_results=no
with the following bazelrc should lead to a coverage.dat file getting generated under bazel-out/_coverage/
coverage.dat
bazel-out/_coverage/
coverage --combined_report=lcov --instrument_test_targets --instrumentation_filter="//" coverage --test_env="LCOV_MERGER=/bin/true"
adding common --experimental_merged_skyframe_analysis_execution to our bazel rc leads to this coverage.dat failing to get generated.
common --experimental_merged_skyframe_analysis_execution
I've also tried, but same issue
build --experimental_merged_skyframe_analysis_execution
No response
tools/bazel coverage //... --cache_test_results=no --experimental_merged_skyframe_analysis_execution --combined_report=lcov --instrument_test_targets --instrumentation_filter="//" --test_env="LCOV_MERGER=/bin/true"
ubuntu 20.04
bazel info release
6.5.0
development version
(@non-git)
git remote get-url origin; git rev-parse HEAD
The text was updated successfully, but these errors were encountered:
Could you test with 7.2.1rc2? There have been a number of fixes related to Skyframe since 6.5.0.
Sorry, something went wrong.
No branches or pull requests
Description of the bug:
with the following bazelrc should lead to a
coverage.dat
file getting generated underbazel-out/_coverage/
adding
common --experimental_merged_skyframe_analysis_execution
to our bazel rc leads to this coverage.dat failing to get generated.I've also tried, but same issue
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.
Which operating system are you running Bazel on?
ubuntu 20.04
What is the output of
bazel info release
?6.5.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 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?
No response
The text was updated successfully, but these errors were encountered: