Parent Log: http://ci.aztec-labs.com/4b713613dbcdc560 Command: 5d6e163c4654d5d0 yarn-project/scripts/run_test.sh pxe/src/synchronizer/synchronizer.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/ada03190841b1923625905b0e6ea3bdc4a3b3e84 Env: REF_NAME=gh-readonly-queue/next/pr-14953-1650b3d017a2a4fa5182c8787e79cc108e24e1f4 CURRENT_VERSION=0.87.6 CI_FULL=0 Date: Thu Jun 12 10:52:56 UTC 2025 System: ARCH=arm64 CPUS=64 MEM=247Gi HOSTNAME=pr-14953_arm64_a1-fast Resources: CPU_LIST=0-63 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_2e465335ef4e0ed8_next 10:52:58 [10:52:58.119] INFO: kv-store:lmdb-v2:test Starting data store with maxReaders 16 10:52:58 [10:52:58.475] INFO: kv-store:lmdb-v2:test Starting data store with maxReaders 16 10:52:58 [10:52:58.906] WARN: pxe:synchronizer Pruning data after block 3 due to reorg 10:52:58 PASS src/synchronizer/synchronizer.test.ts 10:52:58 Synchronizer 10:52:58 ✓ sets header from latest block (357 ms) 10:52:58 ✓ removes notes from db on a reorg (510 ms) 10:52:58 10:52:58 Test Suites: 1 passed, 1 total 10:52:58 Tests: 2 passed, 2 total 10:52:58 Snapshots: 0 total 10:52:58 Time: 1.897 s 10:52:58 Ran all test suites matching /pxe\/src\/synchronizer\/synchronizer.test.ts/i. 10:52:58 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?