Parent Log: http://ci.aztec-labs.com/5c64f73239d8b492 Command: 3b26b88555004035 yarn-project/scripts/run_test.sh pxe/src/synchronizer/synchronizer.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/9cf4a24266245fa3ca003adb00e8ae759880c107 Env: REF_NAME=gh-readonly-queue/next/pr-14963-eeab628a4e44477cb6796c5a461ee0c0bb332d75 CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Mon Jun 16 17:10:25 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-14963_amd64_x1-full Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_2e465335ef4e0ed8_next 17:10:28 [17:10:28.211] INFO: kv-store:lmdb-v2:test Starting data store with maxReaders 16 17:10:28 [17:10:28.738] INFO: kv-store:lmdb-v2:test Starting data store with maxReaders 16 17:10:29 [17:10:29.412] WARN: pxe:synchronizer Pruning data after block 3 due to reorg 17:10:29 PASS src/synchronizer/synchronizer.test.ts 17:10:29 Synchronizer 17:10:29 sets header from latest block (547 ms) 17:10:29 removes notes from db on a reorg (778 ms) 17:10:29 17:10:29 Test Suites: 1 passed, 1 total 17:10:29 Tests: 2 passed, 2 total 17:10:29 Snapshots: 0 total 17:10:29 Time: 2.939 s 17:10:29 Ran all test suites matching pxe/src/synchronizer/synchronizer.test.ts. 17:10:29 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?