Parent Log: http://ci.aztec-labs.com/09c8f962e2d23894 Command: 6d103549f0f4c9d2 yarn-project/scripts/run_test.sh pxe/src/synchronizer/synchronizer.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/534f06e45f48274efd53a2204c90cb0b91a53efb Env: REF_NAME=gh-readonly-queue/next/pr-15230-ad85cda24c2f9b5b4b17d4921f8597b71949bb6c CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Tue Jun 24 20:49:36 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15230_amd64_x2-full Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_2e465335ef4e0ed8_next 20:49:39 [20:49:39.013] INFO: kv-store:lmdb-v2:test Starting data store with maxReaders 16 20:49:39 [20:49:39.490] INFO: kv-store:lmdb-v2:test Starting data store with maxReaders 16 20:49:40 [20:49:40.141] WARN: pxe:synchronizer Pruning data after block 3 due to reorg 20:49:40 PASS src/synchronizer/synchronizer.test.ts 20:49:40 Synchronizer 20:49:40 ✓ sets header from latest block (483 ms) 20:49:40 ✓ removes notes from db on a reorg (786 ms) 20:49:40 20:49:40 Test Suites: 1 passed, 1 total 20:49:40 Tests: 2 passed, 2 total 20:49:40 Snapshots: 0 total 20:49:40 Time: 2.76 s 20:49:40 Ran all test suites matching pxe/src/synchronizer/synchronizer.test.ts. 20:49:40 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?