Parent Log: http://ci.aztec-labs.com/4394d8959cc7e035 Command: 97e7ef9a556fd7e6 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/a3ecf3ea26aad0390dd15cfadbb1d160e85e5f89 Env: REF_NAME=gh-readonly-queue/master/pr-15194-f3a077dd83e56ee0ae0a1175f0dc39fdfa50e6d7 CURRENT_VERSION=0.87.9 CI_FULL=1 Date: Tue Jun 24 17:26:28 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15194_amd64_x2-full Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_ce1d6838f32883da_master 17:26:30 [17:26:30.056] INFO: kv-store:lmdb-v2:sync_data_provider_test Starting data store with maxReaders 16 17:26:30 [17:26:30.115] INFO: kv-store:lmdb-v2:sync_data_provider_test Starting data store with maxReaders 16 17:26:30 PASS src/storage/sync_data_provider/sync_data_provider.test.ts 17:26:30 block header 17:26:30 stores and retrieves the block header (63 ms) 17:26:30 rejects getting header if no block set (24 ms) 17:26:30 17:26:30 Test Suites: 1 passed, 1 total 17:26:30 Tests: 2 passed, 2 total 17:26:30 Snapshots: 0 total 17:26:30 Time: 1.216 s 17:26:30 Ran all test suites matching /pxe\/src\/storage\/sync_data_provider\/sync_data_provider.test.ts/i. 17:26:30 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?