Parent Log: http://ci.aztec-labs.com/78cea4cf271fb3a9 Command: 128a905c1f9c1691 yarn-project/scripts/run_test.sh pxe/src/synchronizer/synchronizer.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/76ca48a2187e3506bb464eae574e49476c2876ca Env: REF_NAME=gh-readonly-queue/next/pr-15045-9d6fb0bd1594726370a5f3a56591963452264642 CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Fri Jun 13 18:05:45 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15045_amd64_x2-full Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_2e465335ef4e0ed8_next 18:05:48 [18:05:48.337] INFO: kv-store:lmdb-v2:test Starting data store with maxReaders 16 18:05:48 [18:05:48.805] INFO: kv-store:lmdb-v2:test Starting data store with maxReaders 16 18:05:49 [18:05:49.394] WARN: pxe:synchronizer Pruning data after block 3 due to reorg 18:05:49 PASS src/synchronizer/synchronizer.test.ts 18:05:49 Synchronizer 18:05:49 sets header from latest block (470 ms) 18:05:49 removes notes from db on a reorg (685 ms) 18:05:49 18:05:49 Test Suites: 1 passed, 1 total 18:05:49 Tests: 2 passed, 2 total 18:05:49 Snapshots: 0 total 18:05:49 Time: 2.611 s 18:05:49 Ran all test suites matching /pxe\/src\/synchronizer\/synchronizer.test.ts/i. 18:05:49 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?