Generate code coverage using source-based LLVM code coverage. #316
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Hi Thomas, I like the potential of this PR for continuous improvement. But I wonder whether it wouldn't be better as a script (either new or option to 'fullbuild.sh"): In CI it only adds runtime but no additional insight as it basically cannot fail --at least for as long as the test does not compare prior run results to flag regressions in code coverage (and fail CI in such cases). Or is your intention to enhance the PR in this way? If so, does it need to build everything (incl. OpenSSL) from scratch, or could it use a pre-existing binary (or cache) to avoid slowing down overall CI performance? |
|
Closing due to inactivity. Retain the goal in #490 . |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No description provided.