Delete nonreduced fuzz inputs #239
Merged
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.
As per the usual process to avoid wasted CI resources and timeouts when CI runs on large and presumed irrelevant inputs.
Normally, deletion of non-reduced fuzz inputs should happen after feature-freeze on the
master
Bitcoin Core branch, but before branch-off, so that the latest release branch retains mostly valid fuzz inputs.Previous: #221
To "reproduce"
Install a fresh VM, as explained in the bash script's doc, and run it:
To "test"
CI
CI should pass, except for a
lint
failure, which should light up on any changes like this pull request, which delete fuzz inputs.