Parent Log: http://ci.aztec-labs.com/8f0e17f4e3d757c2 Command: f8dcf08d5c6024d3 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/254faae7d330e160b14c6eaaa099dc92d4a9cac7 Env: REF_NAME=gh-readonly-queue/next/pr-14870-10badd24359b04680068afd9ca24407383374db1 CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Mon Jun 16 11:53:15 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-14870_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:53:18 [11:53:18.228] INFO: kv-store:lmdb-v2:sync_data_provider_test Starting data store with maxReaders 16 11:53:18 [11:53:18.292] INFO: kv-store:lmdb-v2:sync_data_provider_test Starting data store with maxReaders 16 11:53:18 PASS src/storage/sync_data_provider/sync_data_provider.test.ts 11:53:18 block header 11:53:18 ✓ stores and retrieves the block header (70 ms) 11:53:18 ✓ rejects getting header if no block set (22 ms) 11:53:18 11:53:18 Test Suites: 1 passed, 1 total 11:53:18 Tests: 2 passed, 2 total 11:53:18 Snapshots: 0 total 11:53:18 Time: 1.506 s 11:53:18 Ran all test suites matching /pxe\/src\/storage\/sync_data_provider\/sync_data_provider.test.ts/i. 11:53:18 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?