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