Parent Log: http://ci.aztec-labs.com/91e855bd8ec1fae9 Command: 8f8160a76cd521c1 yarn-project/scripts/run_test.sh pxe/src/synchronizer/synchronizer.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/282da3bd25d49b92970e6fc85f110092e8566299 Env: REF_NAME=gh-readonly-queue/next/pr-14610-ee24aac96469b4f1cb8d70e614b2dd27bf0eb134 CURRENT_VERSION=0.87.6 CI_FULL=0 Date: Tue Jun 24 14:18:14 UTC 2025 System: ARCH=arm64 CPUS=64 MEM=247Gi HOSTNAME=pr-14610_arm64_a1-fast Resources: CPU_LIST=0-63 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_2e465335ef4e0ed8_next 14:18:16 [14:18:16.754] INFO: kv-store:lmdb-v2:test Starting data store with maxReaders 16 14:18:17 [14:18:17.118] INFO: kv-store:lmdb-v2:test Starting data store with maxReaders 16 14:18:17 [14:18:17.590] WARN: pxe:synchronizer Pruning data after block 3 due to reorg 14:18:17 PASS src/synchronizer/synchronizer.test.ts 14:18:17 Synchronizer 14:18:17 sets header from latest block (367 ms) 14:18:17 removes notes from db on a reorg (560 ms) 14:18:17 14:18:17 Test Suites: 1 passed, 1 total 14:18:17 Tests: 2 passed, 2 total 14:18:17 Snapshots: 0 total 14:18:17 Time: 2.112 s 14:18:17 Ran all test suites matching pxe/src/synchronizer/synchronizer.test.ts. 14:18:17 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?