Add Murch’s inputs July 2025 #229

1. 
   murchandamus commented at 2:55 pm on July 2, 2025: contributor

   Merge created using these instructions: https://github.com/murchandamus/fuzzing-helpers
2. Add Murch’s inputs July 2025 055ebce4ec
3. 
   maflcko commented at 8:52 am on July 3, 2025: contributor

   master: https://drahtbot.space/host_reports/DrahtBot/reports/coverage_fuzz/monotree/192743235493eaa0/c93ae8c8e7e3cb34/fuzz.coverage/index.html

   This pull: https://drahtbot.space/host_reports/DrahtBot/reports/coverage_fuzz/monotree/192743235493eaa0/055ebce4ecbd0101/fuzz.coverage/index.html

4. 
   maflcko commented at 8:55 am on July 3, 2025: contributor

   Looks like the line and function coverage did not change at all. This seems a bit odd.

   Happy to merge this, but there may be something wrong with your setup?

5. 
   maflcko commented at 3:27 pm on July 3, 2025: contributor

   For reference, in your last pull there was a nice .3% increase overall: https://github.com/bitcoin-core/qa-assets/pull/225
6. 
   murchandamus commented at 5:50 pm on July 3, 2025: contributor

   I wasn’t fuzzing for a while, due to setting up a new office workstation, and then after recommencing fuzzing missed that the service I had set up didn’t automatically start after restarting my computer, so I have less recent fuzzing before opening this, so I might just not have any additional coverage with your inputs getting merged around the same time. Now everything seems to be up and running again, so I could circle back in a few weeks instead.
7. murchandamus closed this on Jul 3, 2025

   ---

8. 
   maflcko commented at 6:03 pm on July 3, 2025: contributor

   For reference, I compared the coverage on main from before my inputs were merged, so that it can be evaluated independently.

   Sounds good about waiting a few weeks and then circling back.

   As heads up, looking at https://github.com/bitcoin/bitcoin/issues/32275, it could be good to submit new inputs before mid of August and then use end of August to reduce/delete.

9. 
   murchandamus commented at 6:38 pm on July 3, 2025: contributor

   For reference, I compared the coverage on main from before my inputs were merged, so that it can be evaluated independently.

   I see. Maybe I did do something wrong then. Even with having less overall fuzzing time, I would have expected some additional coverage. :thinking: Either way, I think I’ll redo it in a couple weeks then.

Contributors
murchandamus maflcko