add coverage support #282
Open
add coverage support #282
+247
−8
Conversation
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
|
Can you rebase this? Thanks! |
Signed-off-by: Jannik Glückert <[email protected]>
|
Why are we using an HTML parser to parse XML? |
domutils, domhandler and htmlparser2 are essentially one library split into multiple components. They implement both html and xml parsing, and are the most used html/xml parsing library in terms of weekly downloads. |
|
Thank you for the explanation |
|
ping? also, it'd be nice if you could cut a release soon (with or without this PR) because of #281 . The debug functionality is currently useless out of the box. |
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.
This adds coverage support from meson's xml report.
All data exposed by the coverage format is hooked up. This means full line-based coverage, and limited branch coverage (gcovr only tells if a branch site was missed completely or partially, but not which specific branches were missed).
Attributable coverage as introduced in vscode 1.96 is not implemented, as meson currently does not have the necessary facilities.
The coverage API was finalized in vscode 1.88, so bump the minimum accordingly.
This is based on #260 since it makes use of the parallel test execution.