mirror of
https://github.com/bitcoin/bitcoin.git
synced 2026-09-16 08:16:38 +02:00
`setup()` in nanobench runs once per epoch, not once per timed call. If an epoch executes the benchmark body multiple times, `setup()` can silently leave later iterations with different preconditions. Make `setup()` force `epochIterations(1)` itself: keep rejecting incompatible larger explicit epoch sizes, but allow existing single-iteration callers such as `-sanity-check`. With `setup()` handling this centrally, remove the redundant `epochIterations(1)` calls from the benchmarks that use it. Co-authored-by: David Gumberg <davidzgumberg@gmail.com>
5.0 KiB
5.0 KiB