Parent Log: http://ci.aztec-labs.com/7bcd1e743e29abf2 Command: b71f9d6a9e3f68ca yarn-project/scripts/run_test.sh pxe/src/synchronizer/synchronizer.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/ee24aac96469b4f1cb8d70e614b2dd27bf0eb134 Env: REF_NAME=gh-readonly-queue/next/pr-15242-1c2c2ee2949dbe31742cc9501a31bf3bce8083cf CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Tue Jun 24 14:08:10 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15242_amd64_x1-full Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_2e465335ef4e0ed8_next 14:08:12 [14:08:12.979] INFO: kv-store:lmdb-v2:test Starting data store with maxReaders 16 14:08:13 [14:08:13.415] INFO: kv-store:lmdb-v2:test Starting data store with maxReaders 16 14:08:13 [14:08:13.896] WARN: pxe:synchronizer Pruning data after block 3 due to reorg 14:08:13 PASS src/synchronizer/synchronizer.test.ts 14:08:13 Synchronizer 14:08:13 ✓ sets header from latest block (441 ms) 14:08:13 ✓ removes notes from db on a reorg (573 ms) 14:08:13 14:08:13 Test Suites: 1 passed, 1 total 14:08:13 Tests: 2 passed, 2 total 14:08:13 Snapshots: 0 total 14:08:13 Time: 2.466 s 14:08:13 Ran all test suites matching pxe/src/synchronizer/synchronizer.test.ts. 14:08:13 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?