Parent Log: http://ci.aztec-labs.com/90a1e84efe306bbd Command: 97e7ef9a556fd7e6 yarn-project/scripts/run_test.sh pxe/src/synchronizer/synchronizer.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/a229cf871638d3fd774f9272645cc1ac29b8196a Env: REF_NAME=gh-readonly-queue/master/pr-14912-015cb0cadef6a41094c3649f32a735392e1b9693 CURRENT_VERSION=0.87.9 CI_FULL=1 Date: Wed Jun 18 16:02:22 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-14912_amd64_x1-full Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_2e465335ef4e0ed8_master 16:02:24 [16:02:24.461] INFO: kv-store:lmdb-v2:test Starting data store with maxReaders 16 16:02:24 [16:02:24.906] INFO: kv-store:lmdb-v2:test Starting data store with maxReaders 16 16:02:25 [16:02:25.430] WARN: pxe:synchronizer Pruning data after block 3 due to reorg 16:02:25 PASS src/synchronizer/synchronizer.test.ts 16:02:25 Synchronizer 16:02:25 ✓ sets header from latest block (445 ms) 16:02:25 ✓ removes notes from db on a reorg (608 ms) 16:02:25 16:02:25 Test Suites: 1 passed, 1 total 16:02:25 Tests: 2 passed, 2 total 16:02:25 Snapshots: 0 total 16:02:25 Time: 2.369 s 16:02:25 Ran all test suites matching /pxe\/src\/synchronizer\/synchronizer.test.ts/i. 16:02:25 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?