Add Murch’s inputs July 2025

[murchandamus]

Merge created using these instructions: https://github.com/murchandamus/fuzzing-helpers

[maflcko]

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

[maflcko]

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?

[maflcko]

For reference, in your last pull there was a nice .3% increase overall: #225

[murchandamus]

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.

[maflcko]

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 bitcoin/bitcoin#32275, it could be good to submit new inputs before mid of August and then use end of August to reduce/delete.

[murchandamus]

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. 🤔
Either way, I think I’ll redo it in a couple weeks then.