Mutant created against commit 60afa0b.
+1 -1 · cpp
A low-work headers batch that fails continuation should not count as a getheaders response (9f66ac7cf1). With this mutant, it does, so a peer sending a broken batch gets an immediate new getheaders instead of waiting for HEADERS_RESPONSE_TIME.
Commands and environment reported by the submitter
cmake -B build_unit && cmake --build build_unit -j$(nproc)build_unit/bin/test_bitcoin && build_unit/test/functional/test_runner.py`FUZZ=<t> build_fuzz/bin/fuzz qa-assets/fuzz_corpora/<t> -runs=0`..for p2p_headers_presync, process_message, process_messages, cmpctblock, p2p_handshake, p2p_private_broadcastTested at a7acf277dc (base a829aeaac); net_processing changes up to 60afa0b don't touch this path. Survives unit, full functional and fuzz replay. A reach probe (assert(result.success)) fires on p2p_headers_presync, so fuzz reaches failed continuations but nothing checks the getheaders timer afterwards.
Commands are shown as text and never executed by MutantHub.
0 comments
No comments yet
Discuss equivalence, reproduction difficulties, or a test that kills this mutant.