Parent Log: http://ci.aztec-labs.com/d240895a55e41983 Command: 53eb328a1446f762 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/a48851a8c6884f4b9615a154f8862a549722d25e Env: REF_NAME=gh-readonly-queue/next/pr-14680-3b5835195491b53670250790b18c14d922718574 CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Tue Jun 17 11:29:09 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-14680_amd64_x1-full Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_ce1d6838f32883da_next 11:29:11 [11:29:11.902] INFO: kv-store:lmdb-v2:sync_data_provider_test Starting data store with maxReaders 16 11:29:11 [11:29:11.959] INFO: kv-store:lmdb-v2:sync_data_provider_test Starting data store with maxReaders 16 11:29:11 PASS src/storage/sync_data_provider/sync_data_provider.test.ts 11:29:11 block header 11:29:11 stores and retrieves the block header (79 ms) 11:29:11 rejects getting header if no block set (21 ms) 11:29:11 11:29:11 Test Suites: 1 passed, 1 total 11:29:11 Tests: 2 passed, 2 total 11:29:11 Snapshots: 0 total 11:29:11 Time: 1.699 s 11:29:11 Ran all test suites matching pxe/src/storage/sync_data_provider/sync_data_provider.test.ts. 11:29:11 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?