Parent Log: http://ci.aztec-labs.com/ec53a48cfa0deda9 Command: f5e85dbc8a1d83c5 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/26c5a39fe03723d11540f721293d7aebd1f478d9 Env: REF_NAME=gh-readonly-queue/next/pr-14995-75d792847d8434a0c504e7adf5c102a913065272 CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Fri Jun 13 09:01:26 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-14995_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:01:28 [09:01:28.579] INFO: kv-store:lmdb-v2:sync_data_provider_test Starting data store with maxReaders 16 09:01:28 [09:01:28.620] INFO: kv-store:lmdb-v2:sync_data_provider_test Starting data store with maxReaders 16 09:01:28 PASS src/storage/sync_data_provider/sync_data_provider.test.ts 09:01:28 block header 09:01:28 ✓ stores and retrieves the block header (47 ms) 09:01:28 ✓ rejects getting header if no block set (23 ms) 09:01:28 09:01:28 Test Suites: 1 passed, 1 total 09:01:28 Tests: 2 passed, 2 total 09:01:28 Snapshots: 0 total 09:01:28 Time: 1.255 s 09:01:28 Ran all test suites matching /pxe\/src\/storage\/sync_data_provider\/sync_data_provider.test.ts/i. 09:01:28 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?