Bazel coverage is not producing coverage reports for 6.1.2 #18896
Comments
|
Hi @darrenrabbs, Can you provide complete steps to reproduce the above scenario. Thanks! |
|
It should be fixed in up coming 6.3 release by #18791. Would you mind verifying whether that PR fixes your case? |
|
Hi guys, |
|
Bazel 6.2 doesn't have the fix so it's likely you will still have the issue with it. Can you try with a custom binary with #18791 patched, or wait for 6.3.0 RCs? |
|
hmm strange , as I was able to get my coverage.dat created with 6.2.0 for one of my targets. But have not completed testing across all as of yet. |
|
Hi @darrenrabbs, Can you please verify the above with latest 6.3.0. release. Let us know if you still have any queries. Thanks! |
|
Hi, we haven't upgraded to this version as of yet . However, coverage is working for us on 6.2.1 version so we are content for now. Happy to close this also |
Description of the bug:
I am having issues running bazel coverage with the 6.1.2 version of Bazel
This was working fine on 5.4.1 but for some reason now , the _coverage_report.dat files are appearing empty.
Is there anything broken with coverage between the two versions and has anyone discovered any workarounds to resolve?
Thanks
What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
I can see if the steps are reproducible with a simple repo
Which operating system are you running Bazel on?
ubuntu
What is the output of
bazel info release?release 6.1.2
If
bazel info releasereturnsdevelopment versionor(@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?
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: