New inputs from muttfuzz #193

1. 
   agroce commented at 5:02 pm on July 24, 2024: contributor

   Result of running muttfuzz on this target a few days (see https://github.com/agroce/muttfuzz)

   Merge performed using FUZZ=mocked_descriptor_parse src/test/fuzz/fuzz ../qa-assets/fuzz_seed_corpus/mocked_descriptor_parse new_mocked_descriptor_parse_corpus -set_cover_merge=1

   0MERGE-OUTER: successful in 1 attempt(s)
   1MERGE-OUTER: the control file has 266333613 bytes
   2MERGE-OUTER: consumed 134Mb (595Mb rss) to parse the control file
   3MERGE-OUTER: 117 new files with 660 new features added; 10 new coverage edges
   

2. new inputs from muttfuzz 392d6be0ea
3. 
   maflcko commented at 6:07 am on July 25, 2024: contributor

   lgtm: Minimal cov and ft increase:

   https://cirrus-ci.com/task/6557624982831104?logs=ci#L6881:

   0mocked_descriptor_parse                  [#2876](/bitcoin-core-qa-assets/2876/)	DONE   cov: 16902 ft: 98632 corp: 2191/3276Kb lim: 974476 exec/s: 3 rss: 657Mb
   

   https://cirrus-ci.com/task/4855101825744896?logs=ci#L6891 (master):

   0mocked_descriptor_parse                  [#2760](/bitcoin-core-qa-assets/2760/)	DONE   cov: 16901 ft: 97969 corp: 2102/3231Kb lim: 974476 exec/s: 2 rss: 663Mb
   

   However, the fuzz target was recently changed in https://github.com/bitcoin/bitcoin/commit/262260ce1e919613ba60194a5861b0b0a51dfe01, so it may have rediscovered fuzz inputs that previously achieved the same coverage in real code, but were invalidated by the recently added checks (I haven’t checked that).

   Looks good to merge in either case. Thanks!

4. dergoegge merged this on Jul 25, 2024
5. dergoegge closed this on Jul 25, 2024

   ---

6. 
   dergoegge commented at 5:50 pm on July 25, 2024: member

   Thank you Alex!

Contributors
agroce maflcko dergoegge