ci: Split coverage calculation #15780
Merged
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
github-actions
bot
added
internal
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #15780 +/- ##
==========================================
- Coverage 81.36% 80.40% -0.96%
==========================================
Files 1379 1264 -115
Lines 176828 165421 -11407
Branches 2543 0 -2543
==========================================
- Hits 143875 133009 -10866
+ Misses 32471 32412 -59
+ Partials 482 0 -482 ☔ View full report in Codecov by Sentry. |
stinodego
force-pushed
the
coverage-workflow
branch
from
f0ab0b5
to
e6a173c
Compare
stinodego
force-pushed
the
coverage-workflow
branch
from
e6a173c
to
9622b87
Compare
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.
I suspect this will be faster than the current setup when the caching kicks in. Let's see! Otherwise, we can always revert.