Use gcovr instead of lcov in GitHub CI job#27
Merged
Merged
Conversation
rdmark
force-pushed
the
gcovr-workflow
branch
2 times, most recently
from
6bff1bd to
69e6069
Compare
|
Minimum allowed coverage is Generated by 🐒 cobertura-action against cff61bc |
The gcovr tool has more solid support for filtering files to analyze for code coverage
|
Collaborator
Author
|
@msteinert How about this for a solution? I dropped lcov and use gcovr solely. The latter has better support for per-project configurations, so it integrates better with meson and CI. |
Owner
🔥 🔥 🔥 |
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
2 participants
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.
The gcovr tool has more solid support for filtering files to analyze for code coverage