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: #239
To “reproduce”
Install a fresh VM, as explained in the bash script’s doc, and run it:
0apt update && apt install curl -y
1curl -fLO https://raw.githubusercontent.com/bitcoin-core/qa-assets/b30853a993f2fdc2edb8608b4544164d05312428/delete_nonreduced_fuzz_inputs.sh
2bash delete_nonreduced_fuzz_inputs.sh
To “test”
- Keep an eye on coverage stats, to ensure it doesn’t drop
- Re-run the script, to ensure it is “reproducible” to some extent
- Anything else you think is important to test or review
CI
CI should pass, except for a lint failure, which should light up on any changes like this pull request, which delete fuzz inputs.