Parent Log: http://ci.aztec-labs.com/db32bb36b2b5fc89 Command: 963bdac83f923860 yarn-project/scripts/run_test.sh pxe/src/synchronizer/synchronizer.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/f6a105fa6c48358e009a1e84cc8734cc4073459f Env: REF_NAME=gh-readonly-queue/next/pr-15239-0f26f87af2947423f556c64f03e0100cbf5136f7 CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Wed Jun 25 11:29:34 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15239_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:29:37 [11:29:37.254] INFO: kv-store:lmdb-v2:test Starting data store with maxReaders 16 11:29:37 [11:29:37.808] INFO: kv-store:lmdb-v2:test Starting data store with maxReaders 16 11:29:38 [11:29:38.429] WARN: pxe:synchronizer Pruning data after block 3 due to reorg 11:29:38 PASS src/synchronizer/synchronizer.test.ts 11:29:38 Synchronizer 11:29:38 sets header from latest block (560 ms) 11:29:38 removes notes from db on a reorg (759 ms) 11:29:38 11:29:38 Test Suites: 1 passed, 1 total 11:29:38 Tests: 2 passed, 2 total 11:29:38 Snapshots: 0 total 11:29:38 Time: 2.881 s 11:29:38 Ran all test suites matching pxe/src/synchronizer/synchronizer.test.ts. 11:29:38 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?