Parent Log: http://ci.aztec-labs.com/83a09fc9caed2b26 Command: 72b59a67627043b2 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/433ba6218aed45169029991a493e4232b30b8ec6 Env: REF_NAME=gh-readonly-queue/next/pr-15114-23ff13c6b16a0c1333bf26aa5c213054c92403c3 CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Tue Jun 17 17:53:28 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15114_amd64_x1-full Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_ce1d6838f32883da_next 17:53:30 [17:53:30.896] INFO: kv-store:lmdb-v2:sync_data_provider_test Starting data store with maxReaders 16 17:53:30 [17:53:30.944] INFO: kv-store:lmdb-v2:sync_data_provider_test Starting data store with maxReaders 16 17:53:30 PASS src/storage/sync_data_provider/sync_data_provider.test.ts 17:53:30 block header 17:53:30 ✓ stores and retrieves the block header (67 ms) 17:53:30 ✓ rejects getting header if no block set (24 ms) 17:53:30 17:53:30 Test Suites: 1 passed, 1 total 17:53:30 Tests: 2 passed, 2 total 17:53:30 Snapshots: 0 total 17:53:30 Time: 1.481 s 17:53:30 Ran all test suites matching pxe/src/storage/sync_data_provider/sync_data_provider.test.ts. 17:53:30 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?