Parent Log: http://ci.aztec-labs.com/cbf3ddc3cc40e3b7 Command: b2a342c9d927fff0 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/3c1b9d57eadcc8fb03a7ed42610cf0a1ae4a32eb Env: REF_NAME=gh-readonly-queue/next/pr-14858-4b0e4dc09fa55f0bc808fa0c7c3e95e8fa997069 CURRENT_VERSION=0.87.6 CI_FULL=0 Date: Tue Jun 17 21:41:46 UTC 2025 System: ARCH=arm64 CPUS=64 MEM=247Gi HOSTNAME=pr-14858_arm64_a1-fast Resources: CPU_LIST=0-63 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_ce1d6838f32883da_next 21:41:48 [21:41:48.839] INFO: kv-store:lmdb-v2:sync_data_provider_test Starting data store with maxReaders 16 21:41:48 [21:41:48.875] INFO: kv-store:lmdb-v2:sync_data_provider_test Starting data store with maxReaders 16 21:41:48 PASS src/storage/sync_data_provider/sync_data_provider.test.ts 21:41:48 block header 21:41:48 stores and retrieves the block header (44 ms) 21:41:48 rejects getting header if no block set (28 ms) 21:41:48 21:41:48 Test Suites: 1 passed, 1 total 21:41:48 Tests: 2 passed, 2 total 21:41:48 Snapshots: 0 total 21:41:48 Time: 1.184 s 21:41:48 Ran all test suites matching pxe/src/storage/sync_data_provider/sync_data_provider.test.ts. 21:41:48 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?