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