Fix fuzzing corpus collection #2879
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
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## main #2879 +/- ##
==========================================
- Coverage 64.19% 59.93% -4.26%
==========================================
Files 448 448
Lines 23084 23084
==========================================
- Hits 14819 13836 -983
- Misses 7299 8266 +967
- Partials 966 982 +16 see 42 files with indirect coverage changes
Flags with carried forward coverage won't be shown. Click here to find out more. |
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.
Description
Upload fuzzing corpus as an artifact if fuzzing failed for PR (when secrets are not available).
Fix broken corpus collection due to changed Go internals.
Readiness checklist
task all, and it passed.@FerretDB/core), Labels, Project and project's Sprint fields.