Parent Log: http://ci.aztec-labs.com/a362eed6c9743e8a Command: 61c5640c9ec940bf yarn-project/scripts/run_test.sh pxe/src/synchronizer/synchronizer.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/1681cb5bd7c7fb85bd5eb6edb329f577b188bc70 Env: REF_NAME=gh-readonly-queue/next/pr-14910-fe9972873ecbf165d5caaaa2a10c61db0d7189c6 CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Wed Jun 11 16:06:09 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-14910_amd64_x1-full Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_2e465335ef4e0ed8_next 16:06:12 [16:06:12.252] INFO: kv-store:lmdb-v2:test Starting data store with maxReaders 16 16:06:12 [16:06:12.726] INFO: kv-store:lmdb-v2:test Starting data store with maxReaders 16 16:06:13 [16:06:13.301] WARN: pxe:synchronizer Pruning data after block 3 due to reorg 16:06:13 PASS src/synchronizer/synchronizer.test.ts 16:06:13 Synchronizer 16:06:13 ✓ sets header from latest block (461 ms) 16:06:13 ✓ removes notes from db on a reorg (703 ms) 16:06:13 16:06:13 Test Suites: 1 passed, 1 total 16:06:13 Tests: 2 passed, 2 total 16:06:13 Snapshots: 0 total 16:06:13 Time: 2.828 s 16:06:13 Ran all test suites matching /pxe\/src\/synchronizer\/synchronizer.test.ts/i. 16:06:13 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?