Add fuzz inputs

[maflcko]

C.f. last one: #175

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

[maflcko]

https://drahtbot.space/host_reports/DrahtBot/reports/coverage_fuzz/monotree/a786fd2041913d82/3a5592767fa3433f/fuzz.coverage/index.html
https://maflcko.github.io/b-c-cov/fuzz.coverage/index.html

[murchandamus]

I am never quite sure how I’m supposed to read those two coverage reports. 😅

If I read it right, the main branch has no coverage of sha256_avx2.cpp, sha256_sse4.cpp, and sha256_sse41.cpp, while the feature branch has full coverage of those three, but the main branch had full coverage of sha256_x86_shani.cpp and the feature branch has none.
Are these different architectures where only one or the other applies?

Otherwise looks like some nice NgU

[maflcko]

I am never quite sure how I’m supposed to read those two coverage reports. 😅

Yeah, it is a bit unfortunate that they were produced on machines with different hardware. I guess I can try to normalize them in configure somehow.

[maflcko]

Draft for now to look into the timeout.

[maflcko]

Ok, I ran both on the same metal:

• https://drahtbot.space/host_reports/DrahtBot/reports/coverage_fuzz/monotree/949abebea0059edd/cc5858cb70d9ce14/fuzz.coverage/index.html
• https://drahtbot.space/host_reports/DrahtBot/reports/coverage_fuzz/monotree/949abebea0059edd/f7e12aaf658710b7/fuzz.coverage/index.html

[murchandamus]

LGTM

[dergoegge]

Gonna wait for bitcoin/bitcoin#30169

[murchandamus]

Looks like it got merged

[maflcko]

rfm?