aboutsummaryrefslogtreecommitdiff
path: root/src/Makefile.test.include
diff options
context:
space:
mode:
authorlaanwj <126646+laanwj@users.noreply.github.com>2022-05-11 16:28:10 +0200
committerlaanwj <126646+laanwj@users.noreply.github.com>2022-05-17 11:32:25 +0200
commit652b54e53220fedf2c342e428617bcbd2022964d (patch)
tree47e611ad177579f61a0bc64206e8d4daa902f8dc /src/Makefile.test.include
parentb8ded26ef3d7c58a938050659e4c50d850628dff (diff)
downloadbitcoin-652b54e53220fedf2c342e428617bcbd2022964d.tar.xz
bench: Add `--sanity-check` flag, use it in `make check`
The benchmarks are run as part of `make check` for a minimum sanity check. The actual results are being ignored. So only run them for one iteration. This makes the `bench_bitcoin` part take 2m00 instead of 5m20 here. Which is still too long (imo), but this needs to be solved in the `WalletLoading*` benchmarks which take that long per iteration.
Diffstat (limited to 'src/Makefile.test.include')
-rw-r--r--src/Makefile.test.include4
1 files changed, 2 insertions, 2 deletions
diff --git a/src/Makefile.test.include b/src/Makefile.test.include
index 02a3f9ae7d..77ff683974 100644
--- a/src/Makefile.test.include
+++ b/src/Makefile.test.include
@@ -364,8 +364,8 @@ endif
if TARGET_WINDOWS
else
if ENABLE_BENCH
- @echo "Running bench/bench_bitcoin ..."
- $(BENCH_BINARY) > /dev/null
+ @echo "Running bench/bench_bitcoin (one iteration sanity check)..."
+ $(BENCH_BINARY) --sanity-check > /dev/null
endif
endif
$(AM_V_at)$(MAKE) $(AM_MAKEFLAGS) -C secp256k1 check