Parent Log: http://ci.aztec-labs.com/2dd73c7f6b4dcf15 Command: c118fea9c063e772 yarn-project/scripts/run_test.sh pxe/src/synchronizer/synchronizer.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/12d931e5ea9343eec403068931d3121e1d10e37e Env: REF_NAME=gh-readonly-queue/next/pr-15042-254faae7d330e160b14c6eaaa099dc92d4a9cac7 CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Mon Jun 16 12:35:18 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15042_amd64_x1-full Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_2e465335ef4e0ed8_next 12:35:20 [12:35:20.850] INFO: kv-store:lmdb-v2:test Starting data store with maxReaders 16 12:35:21 [12:35:21.348] INFO: kv-store:lmdb-v2:test Starting data store with maxReaders 16 12:35:21 [12:35:21.974] WARN: pxe:synchronizer Pruning data after block 3 due to reorg 12:35:22 PASS src/synchronizer/synchronizer.test.ts 12:35:22 Synchronizer 12:35:22 ✓ sets header from latest block (499 ms) 12:35:22 ✓ removes notes from db on a reorg (745 ms) 12:35:22 12:35:22 Test Suites: 1 passed, 1 total 12:35:22 Tests: 2 passed, 2 total 12:35:22 Snapshots: 0 total 12:35:22 Time: 2.7 s 12:35:22 Ran all test suites matching /pxe\/src\/synchronizer\/synchronizer.test.ts/i. 12:35:22 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?