Parent Log: http://ci.aztec-labs.com/c3e440b46afd0ff2 Command: b5d029682575c433 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/fa4d5ef48c8de52059b5658bbd42e4514386f7db Env: REF_NAME=gh-readonly-queue/next/pr-15073-5ca43853c40a2b8bfbc2148d5fdd46c6f82a74eb CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Mon Jun 16 15:34:27 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15073_amd64_x4-full Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_ce1d6838f32883da_next 15:34:29 [15:34:29.970] INFO: kv-store:lmdb-v2:sync_data_provider_test Starting data store with maxReaders 16 15:34:30 [15:34:30.016] INFO: kv-store:lmdb-v2:sync_data_provider_test Starting data store with maxReaders 16 15:34:30 PASS src/storage/sync_data_provider/sync_data_provider.test.ts 15:34:30 block header 15:34:30 ✓ stores and retrieves the block header (64 ms) 15:34:30 ✓ rejects getting header if no block set (19 ms) 15:34:30 15:34:30 Test Suites: 1 passed, 1 total 15:34:30 Tests: 2 passed, 2 total 15:34:30 Snapshots: 0 total 15:34:30 Time: 1.49 s 15:34:30 Ran all test suites matching pxe/src/storage/sync_data_provider/sync_data_provider.test.ts. 15:34:30 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?