Parent Log: http://ci.aztec-labs.com/e11ece80e16ce810 Command: 6978e0e5f3e9e568 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/db5c19349590089393771b38c3a27e7e65f736a6 Env: REF_NAME=release-please--branches--next CURRENT_VERSION=0.88.0 CI_FULL=0 Date: Mon Jun 23 17:23:05 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=release-please--branches--next_amd64 Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_ce1d6838f32883da_next 17:23:07 [17:23:07.154] INFO: kv-store:lmdb-v2:sync_data_provider_test Starting data store with maxReaders 16 17:23:07 [17:23:07.190] INFO: kv-store:lmdb-v2:sync_data_provider_test Starting data store with maxReaders 16 17:23:07 PASS src/storage/sync_data_provider/sync_data_provider.test.ts 17:23:07 block header 17:23:07 ✓ stores and retrieves the block header (57 ms) 17:23:07 ✓ rejects getting header if no block set (18 ms) 17:23:07 17:23:07 Test Suites: 1 passed, 1 total 17:23:07 Tests: 2 passed, 2 total 17:23:07 Snapshots: 0 total 17:23:07 Time: 1.26 s 17:23:07 Ran all test suites matching pxe/src/storage/sync_data_provider/sync_data_provider.test.ts. 17:23:07 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?