Repository navigation
test: add corpus entries from the FuzzJournalScan and FuzzCheck reruns - #154
Merged
Merged
Conversation
Both targets stopped early on crashers in the first two-hour runs. After the fixes they ran two hours each on .66 without a failure; these are the inputs under 32 KB they found. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
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.
Follow-up to #153. FuzzJournalScan and FuzzCheck stopped early on crashers in their first 2h runs. After the fixes, both ran a full 2h on .66 (8G cap) with no failures: FuzzJournalScan 96M execs, FuzzCheck 968k execs.
This adds the 163 inputs under 32 KB they found. FuzzCheck's seeds now take 3.5s natively. Under -race in CI that adds about 20-30s to the fsck package, whose group still ends well before the goclusterfs group.
🤖 Generated with Claude Code