Parent Log: http://ci.aztec-labs.com/85449a36e9425412 Command: ebfed4061172f77e 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/07aee119a58dd438ddfb5bd53e124e7269e6c651 Env: REF_NAME=gh-readonly-queue/next/pr-15083-9b801754ba98479ee645488c29d2fda1eecbfd85 CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Mon Jun 16 21:05:37 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15083_amd64_x2-full Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_ce1d6838f32883da_next 21:05:39 [21:05:39.350] INFO: kv-store:lmdb-v2:sync_data_provider_test Starting data store with maxReaders 16 21:05:39 [21:05:39.394] INFO: kv-store:lmdb-v2:sync_data_provider_test Starting data store with maxReaders 16 21:05:39 PASS src/storage/sync_data_provider/sync_data_provider.test.ts 21:05:39 block header 21:05:39 ✓ stores and retrieves the block header (63 ms) 21:05:39 ✓ rejects getting header if no block set (20 ms) 21:05:39 21:05:39 Test Suites: 1 passed, 1 total 21:05:39 Tests: 2 passed, 2 total 21:05:39 Snapshots: 0 total 21:05:39 Time: 1.415 s 21:05:39 Ran all test suites matching pxe/src/storage/sync_data_provider/sync_data_provider.test.ts. 21:05:39 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?