Handle "N/A" warning count data when generating summary report #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
Codecov Report
@@ Coverage Diff @@
## main #8 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 2 2
Lines 1545 1561 +16
=========================================
+ Hits 1545 1561 +16
Continue to review full report at Codecov.
|
When it is not possible to compile the sketch at the deltas base ref, the warning count delta is recorded as "N/A". Previously, the summary report generation code did not handle this case correctly, which resulted in failing with an error: TypeError: '>' not supported between instances of 'int' and 'str'
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 it is not possible to compile the sketch at the deltas base ref, the warning count delta is recorded as "N/A".
Previously, the summary report generation code did not handle this case correctly, which resulted in failing with an
error: