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