Parent Log: http://ci.aztec-labs.com/3b68d8ef46724aee Command: 84c999e211bb73e4 yarn-project/scripts/run_test.sh pxe/src/synchronizer/synchronizer.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/3863bc02d671057d0cffd4ced17ca317788ff190 Env: REF_NAME=gh-readonly-queue/staging/pr-15238-db396f13b7ef374a230174bdc4078d9fbb3c788a CURRENT_VERSION=1.0.0 CI_FULL=1 Date: Tue Jun 24 12:13:40 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15238_amd64_x3-full Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_2e465335ef4e0ed8_staging 12:13:43 [12:13:43.030] INFO: kv-store:lmdb-v2:test Starting data store with maxReaders 16 12:13:43 [12:13:43.584] INFO: kv-store:lmdb-v2:test Starting data store with maxReaders 16 12:13:44 [12:13:44.133] WARN: pxe:synchronizer Pruning data after block 3 due to reorg 12:13:44 PASS src/synchronizer/synchronizer.test.ts 12:13:44 Synchronizer 12:13:44 ✓ sets header from latest block (561 ms) 12:13:44 ✓ removes notes from db on a reorg (654 ms) 12:13:44 12:13:44 Test Suites: 1 passed, 1 total 12:13:44 Tests: 2 passed, 2 total 12:13:44 Snapshots: 0 total 12:13:44 Time: 2.825 s 12:13:44 Ran all test suites matching pxe/src/synchronizer/synchronizer.test.ts. 12:13:44 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?