New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for GCOV JSON intermediate format #766
Open
Spacetown
wants to merge
20
commits into
gcovr:main
Choose a base branch
from
Spacetown:read_gcov_json_format
base: main
Could not load branches
Branch not found: {{ refName }}
Could not load tags
Nothing to show
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
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
Spacetown
added
Type: Enhancement
Gcov
Internal change
Internal change not visible to user
labels
Apr 8, 2023
Spacetown
force-pushed
the
read_gcov_json_format
branch
from
April 8, 2023 21:08
abeb40b
to
3168f4a
Compare
Spacetown
force-pushed
the
read_gcov_json_format
branch
from
April 9, 2023 09:33
3168f4a
to
37fb849
Compare
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #766 +/- ##
==========================================
- Coverage 94.65% 94.42% -0.24%
==========================================
Files 50 50
Lines 3913 3997 +84
Branches 825 850 +25
==========================================
+ Hits 3704 3774 +70
- Misses 130 143 +13
- Partials 79 80 +1 ☔ View full report in Codecov by Sentry. |
Spacetown
force-pushed
the
read_gcov_json_format
branch
2 times, most recently
from
April 12, 2023 20:11
f131ed7
to
0941f68
Compare
Pesa
reviewed
Apr 14, 2023
Spacetown
force-pushed
the
read_gcov_json_format
branch
from
April 16, 2023 20:03
0941f68
to
6c2252d
Compare
Spacetown
force-pushed
the
read_gcov_json_format
branch
from
May 4, 2024 22:01
ba4dc42
to
0a89bb8
Compare
Spacetown
force-pushed
the
read_gcov_json_format
branch
from
May 6, 2024 18:59
adca518
to
8810168
Compare
Spacetown
force-pushed
the
read_gcov_json_format
branch
from
May 6, 2024 21:24
8810168
to
e7d57c9
Compare
.gcov files are useable when debug |
??? |
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.
GCOV introduced a JSON intermediate format with version 9.1.
If the gcov help contains the option
--json-format
this option is used to get compressed JSON files (.join.gz
) instead of the human readable files (.gcov
). The compressed JSON files are only used if the calls are excluded (default) because the call information isn't present in the JSON format yet.Closes #282