Parent Log: http://ci.aztec-labs.com/c148bc90788ce605 Command: 069d70048f6bf27e 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/08d3f55874836a573c4756b0cc7279160b0813a3 Env: REF_NAME=gh-readonly-queue/next/pr-15167-aac426c9418162aeee8162ed45014b9393d605b8 CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Fri Jun 20 10:05:48 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15167_amd64_x3-full Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_ce1d6838f32883da_next 10:05:51 [10:05:51.221] INFO: kv-store:lmdb-v2:sync_data_provider_test Starting data store with maxReaders 16 10:05:51 [10:05:51.263] INFO: kv-store:lmdb-v2:sync_data_provider_test Starting data store with maxReaders 16 10:05:51 PASS src/storage/sync_data_provider/sync_data_provider.test.ts 10:05:51 block header 10:05:51 stores and retrieves the block header (74 ms) 10:05:51 rejects getting header if no block set (28 ms) 10:05:51 10:05:51 Test Suites: 1 passed, 1 total 10:05:51 Tests: 2 passed, 2 total 10:05:51 Snapshots: 0 total 10:05:51 Time: 1.569 s 10:05:51 Ran all test suites matching pxe/src/storage/sync_data_provider/sync_data_provider.test.ts. 10:05:51 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?