Parent Log: http://ci.aztec-labs.com/88fdb72b2f06aef3 Command: 24e90b7895ff1ed6 yarn-project/scripts/run_test.sh pxe/src/synchronizer/synchronizer.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/8cc8a56892d36191eefb49254ebbe49ea99ef4b8 Env: REF_NAME=gh-readonly-queue/next/pr-14921-78d87cb88633aee537d022d6fd8e57ceb74a3a95 CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Wed Jun 18 11:34:21 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-14921_amd64_x4-full Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_2e465335ef4e0ed8_next 11:34:24 [11:34:24.402] INFO: kv-store:lmdb-v2:test Starting data store with maxReaders 16 11:34:24 [11:34:24.957] INFO: kv-store:lmdb-v2:test Starting data store with maxReaders 16 11:34:25 [11:34:25.602] WARN: pxe:synchronizer Pruning data after block 3 due to reorg 11:34:25 PASS src/synchronizer/synchronizer.test.ts 11:34:25 Synchronizer 11:34:25 ✓ sets header from latest block (574 ms) 11:34:25 ✓ removes notes from db on a reorg (738 ms) 11:34:25 11:34:25 Test Suites: 1 passed, 1 total 11:34:25 Tests: 2 passed, 2 total 11:34:25 Snapshots: 0 total 11:34:25 Time: 2.932 s 11:34:25 Ran all test suites matching pxe/src/synchronizer/synchronizer.test.ts. 11:34:25 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?