Created following the procedure specified in https://github.com/murchandamus/fuzzing-helpers/blob/master/README.md#upstreaming-the-results-about-every-two-months
Add Murch’s inputs April 2026 #271
pull murchandamus wants to merge 1 commits into bitcoin-core:main from murchandamus:2026-04-murch-inputs changing 0 files +0 −0-
murchandamus commented at 9:55 PM on April 7, 2026: contributor
-
maflcko commented at 9:03 AM on April 8, 2026: contributor
I think this is based on the wrong month?
$ git log 926238adcf17640ecd1a327597094372a4ea9b5e -2 commit 926238adcf17640ecd1a327597094372a4ea9b5e Author: Murch <murch@murch.one> Date: Tue Apr 7 14:53:08 2026 -0700 Add Murch’s inputs April 2026 commit c19a207dc6e5f50a1d4ad6cb1c4a73b7906f69ea Merge: eac1c57614d 0eeb79769bf Author: maflcko <6399679+maflcko@users.noreply.github.com> Date: Thu Jan 29 19:06:40 2026 +0100 -
murchandamus commented at 4:04 PM on April 8, 2026: contributor
Ah crap. Will redo and resubmit later today.
-
Add Murch’s inputs April 2026 dbf11265aa
- murchandamus force-pushed on Apr 8, 2026
-
murchandamus commented at 8:08 PM on April 8, 2026: contributor
I was wondering why it was so big, but I didn’t realize that I must have checked out from an old state which then made me restore all the inputs that had just been pruned.
I hope this one makes more sense.
-
maflcko commented at 9:41 AM on April 9, 2026: contributor
The size increase is still 2.6 -> 3.6 GB, but this may be fine. Let me run the coverage script ...
-
maflcko commented at 11:46 AM on April 9, 2026: contributor
- maflcko merged this on Apr 9, 2026
- maflcko closed this on Apr 9, 2026
