Parent Log: http://ci.aztec-labs.com/fc42a3a7694a8fcc Command: 84c999e211bb73e4 BENCH_OUTPUT=bench-out/kv_store.bench.json yarn-project/scripts/run_test.sh kv-store/src/bench/map_bench.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/3863bc02d671057d0cffd4ced17ca317788ff190 Env: REF_NAME=gh-readonly-queue/staging/pr-15238-db396f13b7ef374a230174bdc4078d9fbb3c788a CURRENT_VERSION=1.0.0 CI_FULL=1 Date: Tue Jun 24 12:30:49 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15238_amd64_x1-full Resources: CPU_LIST=15,32 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_313c4a4ebc6276aa_staging 12:30:51 [12:30:51.248] INFO: kv-store:lmdb-v2:test Starting data store with maxReaders 16 12:30:53 [12:30:53.503] INFO: kv-store:lmdb-v2:test Starting data store with maxReaders 16 12:30:54 [12:30:54.994] INFO: kv-store:lmdb-v2:test Starting data store with maxReaders 16 12:30:56 [12:30:56.048] INFO: kv-store:lmdb-v2:test Starting data store with maxReaders 16 12:30:56 [12:30:56.398] INFO: kv-store:lmdb-v2:test Starting data store with maxReaders 16 12:30:57 PASS src/bench/map_bench.test.ts (6.335 s) 12:30:57 LMDBMap benchmarks 12:30:57 ✓ adds individual values (2255 ms) 12:30:57 ✓ adds batched values (1491 ms) 12:30:57 ✓ reads individual values (1053 ms) 12:30:57 ✓ reads via a cursor (349 ms) 12:30:57 ✓ reads the size of the map (644 ms) 12:30:57 12:30:57 Test Suites: 1 passed, 1 total 12:30:57 Tests: 5 passed, 5 total 12:30:57 Snapshots: 0 total 12:30:57 Time: 6.408 s 12:30:57 Ran all test suites matching kv-store/src/bench/map_bench.test.ts. 12:30:57 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?