Pruning large/slow inputs? about qa-assets HOT 8 CLOSED

Yeah, it is really simple. See #97

Make sure to set up a fresh Jammy VM for this, as documented in the bash script.

from qa-assets.

Ok, I'll run the script and create the pull today. Anyone is then invited to review, if they want.

from qa-assets.

Yes, this is done at or around the branch-off point for every release. See pulls

from qa-assets.

(The reason this is done at around the branch-off point is that the then resulting fuzz inputs will be "valid" for the longest duration for the latest release branch)

from qa-assets.

@dergoegge Is someone working on this? If not, I'll do it.

from qa-assets.

@MarcoFalke Not working on this currently. I've also never done this before so you doing it is probably best (unless there is an easy command/script to run?).

I've been meaning to write some docs for the usual processes in this repo (merging, pruning, maybe linking to the Bitcoin Core fuzzing docs?). Will follow up with that separately.

from qa-assets.

See #119, I think this can be closed now?

from qa-assets.

Think we can add some additional notes/here (@dergoegge may follow up), but I'll close this for now.

from qa-assets.