Add handling for branch coverage information from CTest#3598
Merged
williamjallen merged 1 commit intoApr 10, 2026
Merged
Conversation
da1a747 to
4cf01c7
Compare
Member
Author
|
Converting back to draft. The coverage display of a real submission only showed the branch information |
4cf01c7 to
c8dbdf6
Compare
williamjallen
requested changes
Apr 9, 2026
c8dbdf6 to
4445cbd
Compare
williamjallen
requested changes
Apr 10, 2026
Collaborator
williamjallen
left a comment
There was a problem hiding this comment.
A couple stylistic things to fix and then this should be good to go.
When reading the coverage log file, look for incoming "BranchesTested" and "BranchesUntested" attributes on each log line. If either is greater than 0, add a branch entry to that line.
4445cbd to
9567114
Compare
williamjallen
approved these changes
Apr 10, 2026
This file contains hidden or 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
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.
When reading the coverage log file, look for incoming "BranchesTested" and "BranchesUntested" attributes on each log line. If either is greater than 0, add a branch entry to that line.