Parent Log: http://ci.aztec-labs.com/3e13a93e0258dba1 Command: 47858aa9bf665f8a yarn-project/scripts/run_test.sh pxe/src/synchronizer/synchronizer.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/1bb4f0588a9dc5b1df622753aab1d907b3f12c7a Env: REF_NAME=gh-readonly-queue/next/pr-15245-534f06e45f48274efd53a2204c90cb0b91a53efb CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Wed Jun 25 08:18:50 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15245_amd64_x4-full Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_2e465335ef4e0ed8_next 08:18:53 [08:18:53.056] INFO: kv-store:lmdb-v2:test Starting data store with maxReaders 16 08:18:53 [08:18:53.576] INFO: kv-store:lmdb-v2:test Starting data store with maxReaders 16 08:18:54 [08:18:54.135] WARN: pxe:synchronizer Pruning data after block 3 due to reorg 08:18:54 PASS src/synchronizer/synchronizer.test.ts 08:18:54 Synchronizer 08:18:54 ✓ sets header from latest block (525 ms) 08:18:54 ✓ removes notes from db on a reorg (680 ms) 08:18:54 08:18:54 Test Suites: 1 passed, 1 total 08:18:54 Tests: 2 passed, 2 total 08:18:54 Snapshots: 0 total 08:18:54 Time: 2.726 s 08:18:54 Ran all test suites matching pxe/src/synchronizer/synchronizer.test.ts. 08:18:54 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?