maflcko

Is this still an issue after qt was bumped from 5.9 to 5.12 in Bitcoin Core 22.x in depends: https://github.com/bitcoin/bitcoin/commit/06cd0da21fc14360e10204affe240b72715a0267#diff-0d7e256978e78897b774581dad22102138ce4ba46aa07faaef1ae6fc6178aad4 ? Also, 23.x has qt bumped from 5.12 to 5.15...

Is this still an issue with 23.x?

Sounds good. Do you want to create a patch?

What is `tail ./fuzz-*.log` ?

Ah, so I guess this is expected, because it is loading all fuzz inputs. (The same would happen on merge or on `-runs=1`). This should be fixed the next time...

See https://github.com/bitcoin/bitcoin/commit/2b3f43b96ef0b674bf350f50f317477b8d3e1e56

I don't know how to reduce the runtime further. Maybe assumeutxo can be used? If not, the only alternative would be to remove the target.

DrahtBot can (manually triggered) create html coverage reports. See https://github.com/maflcko/DrahtBot/blob/main/coverage_fuzz/src/main.rs#L151 and https://drahtbot.space/host_reports/DrahtBot/reports/coverage_fuzz/monotree/004367dba8a3e852/428a2e7b0def5102/fuzz.coverage/index.html libFuzzer could also be used by using the `ft` metric, printed from the summary. Example: ``` #1206 DONE...

Fixed in https://github.com/bitcoin/bitcoin/pull/29329

I think for now the comparison can be done manually, but a CI task to run `diff` on the previous CI tasks' output can be added.