Parent Log: http://ci.aztec-labs.com/b19cd8e5b38225d7 Command: f1d5df06d37e0c0f 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/5c77169d7f01a9e15bc19b05fa231fd96111d7dd Env: REF_NAME=gh-readonly-queue/next/pr-15042-d5c48d855d83e19712c6b72281801c6fce176ec1 CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Wed Jun 18 15:01:48 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15042_amd64_x3-full Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_ce1d6838f32883da_next 15:01:51 [15:01:51.302] INFO: kv-store:lmdb-v2:sync_data_provider_test Starting data store with maxReaders 16 15:01:51 [15:01:51.353] INFO: kv-store:lmdb-v2:sync_data_provider_test Starting data store with maxReaders 16 15:01:51 PASS src/storage/sync_data_provider/sync_data_provider.test.ts 15:01:51 block header 15:01:51 ✓ stores and retrieves the block header (69 ms) 15:01:51 ✓ rejects getting header if no block set (37 ms) 15:01:51 15:01:51 Test Suites: 1 passed, 1 total 15:01:51 Tests: 2 passed, 2 total 15:01:51 Snapshots: 0 total 15:01:51 Time: 1.683 s 15:01:51 Ran all test suites matching pxe/src/storage/sync_data_provider/sync_data_provider.test.ts. 15:01:51 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?