Parent Log: http://ci.aztec-labs.com/c03ea752b0af6173 Command: 61f8e44af0fc4001 yarn-project/scripts/run_test.sh pxe/src/synchronizer/synchronizer.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/e56baa7f24bac54baf9e2f22f6f33ae6fa8b8c0f Env: REF_NAME=gh-readonly-queue/next/pr-14891-76ca48a2187e3506bb464eae574e49476c2876ca CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Fri Jun 13 19:21:36 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-14891_amd64_x1-full Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_2e465335ef4e0ed8_next 19:21:38 [19:21:38.827] INFO: kv-store:lmdb-v2:test Starting data store with maxReaders 16 19:21:39 [19:21:39.285] INFO: kv-store:lmdb-v2:test Starting data store with maxReaders 16 19:21:39 [19:21:39.839] WARN: pxe:synchronizer Pruning data after block 3 due to reorg 19:21:39 PASS src/synchronizer/synchronizer.test.ts 19:21:39 Synchronizer 19:21:39 ✓ sets header from latest block (459 ms) 19:21:39 ✓ removes notes from db on a reorg (643 ms) 19:21:39 19:21:39 Test Suites: 1 passed, 1 total 19:21:39 Tests: 2 passed, 2 total 19:21:39 Snapshots: 0 total 19:21:39 Time: 2.565 s 19:21:39 Ran all test suites matching /pxe\/src\/synchronizer\/synchronizer.test.ts/i. 19:21:39 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?