Parent Log: http://ci.aztec-labs.com/21de0fcccf3c1198 Command: 5b4d9f16dc72b5a7 yarn-project/scripts/run_test.sh pxe/src/synchronizer/synchronizer.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/1b10c7d500621ca2e4c0db764df67f3085beb282 Env: REF_NAME=gh-readonly-queue/next/pr-15229-99e234fe4473771b32124e0402885610a6a3f98a CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Tue Jun 24 10:04:49 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15229_amd64_x1-full Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_2e465335ef4e0ed8_next 10:04:52 [10:04:52.075] INFO: kv-store:lmdb-v2:test Starting data store with maxReaders 16 10:04:52 [10:04:52.595] INFO: kv-store:lmdb-v2:test Starting data store with maxReaders 16 10:04:53 [10:04:53.326] WARN: pxe:synchronizer Pruning data after block 3 due to reorg 10:04:53 PASS src/synchronizer/synchronizer.test.ts 10:04:53 Synchronizer 10:04:53 ✓ sets header from latest block (524 ms) 10:04:53 ✓ removes notes from db on a reorg (850 ms) 10:04:53 10:04:53 Test Suites: 1 passed, 1 total 10:04:53 Tests: 2 passed, 2 total 10:04:53 Snapshots: 0 total 10:04:53 Time: 2.83 s 10:04:53 Ran all test suites matching pxe/src/synchronizer/synchronizer.test.ts. 10:04:53 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?