Add fuzz inputs #227

C.f. last one: #220

mv fuzz_corpora fuzz_inputs_moved
../bitcoin-core/bld/test/fuzz/test_runner.py -l DEBUG --par $( nproc ) --m_dir ./fuzz_inputs_moved/  --m_dir ./results_from_working_farm --m_dir ../etc/... ./fuzz_corpora
git restore -- ./fuzz_corpora
git add ./fuzz_corpora
git commit -m "Add fuzz inputs"

lol, I noticed that I was clashing with Niklas on even months, so I moved to odd months and now I’m one hour next to you.

mine are pretty random and not on a schedule, looking back, it was rare for me to open early in the month. Not sure how to proceed, but I'll take another look tomorrow when all CI passed.

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/7720cbb5d7d63e03/fuzz.coverage/index.html

Looks like mini_miner is now the slowest target: https://cirrus-ci.com/task/6602192649453568?logs=ci#L5428

Maybe a follow-up can deal with speeding it up, but this should be good to merge?

Looks like mini_miner is now the slowest target: https://cirrus-ci.com/task/6602192649453568?logs=ci#L5428

Maybe a follow-up can deal with speeding it up, but this should be good to merge?

tbh I think we can rewrite it using txgraph now 🤔