Parent Log: http://ci.aztec-labs.com/9a8b51ad4daf16b0 Command: 426cee6a32f1da3c 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/d96baf1c44329e8b2e3a432ad803f702f5184a62 Env: REF_NAME=gh-readonly-queue/next/pr-15025-26c5a39fe03723d11540f721293d7aebd1f478d9 CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Fri Jun 13 09:33:05 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15025_amd64_x4-full Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_ce1d6838f32883da_next 09:33:08 [09:33:08.082] INFO: kv-store:lmdb-v2:sync_data_provider_test Starting data store with maxReaders 16 09:33:08 [09:33:08.133] INFO: kv-store:lmdb-v2:sync_data_provider_test Starting data store with maxReaders 16 09:33:08 PASS src/storage/sync_data_provider/sync_data_provider.test.ts 09:33:08 block header 09:33:08 ✓ stores and retrieves the block header (57 ms) 09:33:08 ✓ rejects getting header if no block set (20 ms) 09:33:08 09:33:08 Test Suites: 1 passed, 1 total 09:33:08 Tests: 2 passed, 2 total 09:33:08 Snapshots: 0 total 09:33:08 Time: 1.485 s 09:33:08 Ran all test suites matching /pxe\/src\/storage\/sync_data_provider\/sync_data_provider.test.ts/i. 09:33:08 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?