merge-script b858b72903
Merge bitcoin/bitcoin#31841: fuzz: Use immediate task runner to increase fuzz stability
fa4fb6a8f15c295a2a3d3ffd737e115b8be46c1f fuzz: Use serial task runner to increase fuzz stability (MarcoFalke)

Pull request description:

  Leaking a scheduler with a non-empty queue from the fuzz initialization phase into the fuzz target execution phase is problematic, because it messes with coverage data. This in turn is problematic, because it leads to:

  * Decrease in fuzz target execution stability (non-determinism when running the fuzz target).
  * Decrease in fuzz input merge stability (non-determinism when selecting a minimum set of fuzz input to reach maximum coverage), which leads to qa-assets bloat.

  Fix one such issue. Tracking issue: https://github.com/bitcoin/bitcoin/issues/29018

  Can be tested via: `RUST_BACKTRACE=1 cargo run --manifest-path ./contrib/devtools/deterministic-fuzz-coverage/Cargo.toml -- $PWD/bld-cmake $PWD/../b-c-qa-assets/fuzz_corpora/ partially_downloaded_block`.

  The failure is non-deterministic (obviously) and will show coverage in validation signals such as `UpdatedBlockTip` before this change and will have this one fixed after this change.

ACKs for top commit:
  marcofleon:
    ACK fa4fb6a8f15c295a2a3d3ffd737e115b8be46c1f
  dergoegge:
    Code review ACK fa4fb6a8f15c295a2a3d3ffd737e115b8be46c1f

Tree-SHA512: fd1f66562c1d3c21553c7dd324399cdc16faa2fedfdb8e7544ea6a68b8b356e7c81d81815ecf70e0d334307dab6b275c1889b3b889b6f15eec514beee22c95f4
2025-03-21 08:25:41 +08:00
..
2025-03-13 11:13:13 +00:00
2025-03-13 11:13:13 +00:00
2025-03-13 11:13:13 +00:00
2024-10-25 18:09:36 +01:00
2025-03-13 11:13:13 +00:00
2025-03-13 11:13:13 +00:00
2024-11-26 20:47:08 -05:00
2024-12-05 14:37:47 +00:00
2025-03-13 11:13:13 +00:00
2024-11-04 14:19:40 -05:00
2024-05-20 16:48:19 +00:00
2024-07-08 11:12:01 +02:00
2025-01-22 11:29:05 +01:00
2025-01-22 11:29:05 +01:00
2024-07-08 11:12:01 +02:00
2024-12-31 00:04:20 -03:00
2024-12-31 00:04:20 -03:00
2025-03-13 11:13:13 +00:00