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