Parent Log: http://ci.aztec-labs.com/4c9c6ce753b843f4 Command: 6d103549f0f4c9d2 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/534f06e45f48274efd53a2204c90cb0b91a53efb Env: REF_NAME=gh-readonly-queue/next/pr-15230-ad85cda24c2f9b5b4b17d4921f8597b71949bb6c CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Tue Jun 24 20:49:41 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15230_amd64_x1-full Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_ce1d6838f32883da_next 20:49:43 [20:49:43.566] INFO: kv-store:lmdb-v2:sync_data_provider_test Starting data store with maxReaders 16 20:49:43 [20:49:43.608] INFO: kv-store:lmdb-v2:sync_data_provider_test Starting data store with maxReaders 16 20:49:43 PASS src/storage/sync_data_provider/sync_data_provider.test.ts 20:49:43 block header 20:49:43 ✓ stores and retrieves the block header (56 ms) 20:49:43 ✓ rejects getting header if no block set (21 ms) 20:49:43 20:49:43 Test Suites: 1 passed, 1 total 20:49:43 Tests: 2 passed, 2 total 20:49:43 Snapshots: 0 total 20:49:43 Time: 1.406 s 20:49:43 Ran all test suites matching pxe/src/storage/sync_data_provider/sync_data_provider.test.ts. 20:49:43 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?