Parent Log: http://ci.aztec-labs.com/516fa63e1f82d416 Command: 97e7ef9a556fd7e6 yarn-project/scripts/run_test.sh aztec-node/src/sentinel/store.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/f3a077dd83e56ee0ae0a1175f0dc39fdfa50e6d7 Env: REF_NAME=gh-readonly-queue/master/pr-14734-a229cf871638d3fd774f9272645cc1ac29b8196a CURRENT_VERSION=0.87.9 CI_FULL=1 Date: Tue Jun 24 10:39:14 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-14734_amd64_x1-full Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_970b4858ee6859a0_master 10:39:15 [10:39:15.418] INFO: kv-store:lmdb-v2:sentinel-store-test Starting data store with maxReaders 16 10:39:15 [10:39:15.465] INFO: kv-store:lmdb-v2:sentinel-store-test Starting data store with maxReaders 16 10:39:15 [10:39:15.500] INFO: kv-store:lmdb-v2:sentinel-store-test Starting data store with maxReaders 16 10:39:15 PASS src/sentinel/store.test.ts 10:39:15 sentinel-store 10:39:15 ✓ inserts new validators with all statuses (37 ms) 10:39:15 ✓ updates existing validators with new slots and inserts new ones (35 ms) 10:39:15 ✓ trims history to the specified length (51 ms) 10:39:15 10:39:15 Test Suites: 1 passed, 1 total 10:39:15 Tests: 3 passed, 3 total 10:39:15 Snapshots: 0 total 10:39:15 Time: 0.665 s 10:39:15 Ran all test suites matching /aztec-node\/src\/sentinel\/store.test.ts/i. 10:39:15 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?