I noticed there was no corpus for three harnesses that recently got added, so I created some initial inputs.
I followed the same process for each one outlined in the most recent open pull request. Started with inputs from the other directories.
FUZZ=package_rbf src/test/fuzz/fuzz -set_cover_merge=1 -shuffle=0 -prefer_small=1 -use_value_profile=0 ../qa-assets/fuzz_seed_corpus/package_rbf ../qa-assets/fuzz_seed_corpus/*
Then came up with inputs from scratch (let that run for a bit).
FUZZ=package_rbf src/test/fuzz/fuzz -jobs=4 -prefer_small=1 ../qa-assets/fuzz_seed_corpus/package_rbf_new
Then merged those two directories to get the final corpus.
FUZZ=package_rbf src/test/fuzz/fuzz -set_cover_merge=1 -shuffle=0 -prefer_small=1 -use_value_profile=0 ../qa-assets/fuzz_seed_corpus/package_rbf ../qa-assets/fuzz_seed_corpus/package_rbf_new
Here is the coverage summary:
0python3 ./test/fuzz/test_runner.py ../qa-assets/fuzz_seed_corpus feefrac build_and_compare_feerate_diagram package_rbf
13 of 177 detected fuzz target(s) selected: build_and_compare_feerate_diagram feefrac package_rbf
2Summary:
3build_and_compare_feerate_diagram [#54](/bitcoin-core-qa-assets/54/) DONE cov: 145 ft: 746 corp: 53/1099Kb lim: 1048551 exec/s: 0 rss: 38Mb
4feefrac [#28](/bitcoin-core-qa-assets/28/) DONE cov: 113 ft: 113 corp: 27/571b lim: 129 exec/s: 0 rss: 33Mb
5package_rbf [#434](/bitcoin-core-qa-assets/434/) DONE cov: 1818 ft: 9496 corp: 420/26Mb lim: 1048576 exec/s: 434 rss: 253Mb