Parent Log: http://ci.aztec-labs.com/e09dcc0d0838bc1c Command: 56d3c530a47f3a72 yarn-project/scripts/run_test.sh pxe/src/storage/sync_data_provider/sync_data_provider.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/9071986bfe3af58c70d2c80c10f523e22bfe4cb4 Env: REF_NAME=gh-readonly-queue/next/pr-15133-64d1ec347b1cea9fa1b04ff6fc2984f8ee073b2b CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Fri Jun 20 14:52:28 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15133_amd64_x3-full Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_ce1d6838f32883da_next 14:52:30 [14:52:30.630] INFO: kv-store:lmdb-v2:sync_data_provider_test Starting data store with maxReaders 16 14:52:30 [14:52:30.666] INFO: kv-store:lmdb-v2:sync_data_provider_test Starting data store with maxReaders 16 14:52:30 PASS src/storage/sync_data_provider/sync_data_provider.test.ts 14:52:30 block header 14:52:30 ✓ stores and retrieves the block header (55 ms) 14:52:30 ✓ rejects getting header if no block set (18 ms) 14:52:30 14:52:30 Test Suites: 1 passed, 1 total 14:52:30 Tests: 2 passed, 2 total 14:52:30 Snapshots: 0 total 14:52:30 Time: 1.437 s 14:52:30 Ran all test suites matching pxe/src/storage/sync_data_provider/sync_data_provider.test.ts. 14:52:30 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?