Closed tobithiel closed 1 year ago
Thanks for this! I think it makes sense to change one of the CI targets to call bazel coverage
instead of bazel test
. I can do it after we merge this, no problem.
Thanks for this! I think it makes sense to change one of the CI targets to call
bazel coverage
instead ofbazel test
. I can do it after we merge this, no problem.
No problem, thanks for the project. I gave it a try, but I can't really test it since I'm not sure how to actually trigger CI (or don't have permissions to). So feel free to revert and do it differently.
I'll get to it today.
@f0rmiga Could you take another look please when you have some time? I merged in main
to resolve the conflicts and use the new CI stuff.
Awesome, thanks!
Type of change
bazel coverage <...>
with C/C++ targets was not working because thegcov
binary was not included in the runfiles. This was showing as a silent failure as an empty coverage report. The test log contains:Test plan