Fix coverage calculation by calling blaze coverage
individually
#565
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Setting LCOV_MERGER (as done in bazelbuild/rules_apple#338 (comment)) results in
blaze coverage
of a test_suite collecting the test coverage of one test in the suite (presumably, the slowest test to complete). We can fix this by callingblaze coverage
of all tests and then merging them afterwards.We also want to avoid getting coverage of non-Santa binaries packaged in runfiles as testdata.