Parent Log: http://ci.aztec-labs.com/8dcffbbcc559db48 Command: 85ebe83a9ef9464b yarn-project/scripts/run_test.sh pxe/src/synchronizer/synchronizer.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/24972303091baff6f83c6389d7d1406c932357e9 Env: REF_NAME=gh-readonly-queue/next/pr-15042-a0a8617413ca6f4fba2ad190ce73dab59bd75a45 CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Tue Jun 17 14:17:14 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15042_amd64_x3-full Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_2e465335ef4e0ed8_next 14:17:16 [14:17:16.918] INFO: kv-store:lmdb-v2:test Starting data store with maxReaders 16 14:17:17 [14:17:17.454] INFO: kv-store:lmdb-v2:test Starting data store with maxReaders 16 14:17:18 [14:17:18.046] WARN: pxe:synchronizer Pruning data after block 3 due to reorg 14:17:18 PASS src/synchronizer/synchronizer.test.ts 14:17:18 Synchronizer 14:17:18 ✓ sets header from latest block (553 ms) 14:17:18 ✓ removes notes from db on a reorg (692 ms) 14:17:18 14:17:18 Test Suites: 1 passed, 1 total 14:17:18 Tests: 2 passed, 2 total 14:17:18 Snapshots: 0 total 14:17:18 Time: 2.828 s 14:17:18 Ran all test suites matching pxe/src/synchronizer/synchronizer.test.ts. 14:17:18 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?