Parent Log: http://ci.aztec-labs.com/7ec536495953bb64 Command: 70462c95d683706b yarn-project/scripts/run_test.sh pxe/src/synchronizer/synchronizer.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/fa159c5d52a45358479f951a547fed37f141a6ed Env: REF_NAME=gh-readonly-queue/next/pr-15054-184d5f7d956dd7251670a2dd6728f313cfdf3caf CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Fri Jun 13 22:56:36 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15054_amd64_x1-full Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_2e465335ef4e0ed8_next 22:56:39 [22:56:39.038] INFO: kv-store:lmdb-v2:test Starting data store with maxReaders 16 22:56:39 [22:56:39.547] INFO: kv-store:lmdb-v2:test Starting data store with maxReaders 16 22:56:40 [22:56:40.160] WARN: pxe:synchronizer Pruning data after block 3 due to reorg 22:56:40 PASS src/synchronizer/synchronizer.test.ts 22:56:40 Synchronizer 22:56:40 sets header from latest block (510 ms) 22:56:40 removes notes from db on a reorg (751 ms) 22:56:40 22:56:40 Test Suites: 1 passed, 1 total 22:56:40 Tests: 2 passed, 2 total 22:56:40 Snapshots: 0 total 22:56:40 Time: 2.579 s 22:56:40 Ran all test suites matching /pxe\/src\/synchronizer\/synchronizer.test.ts/i. 22:56:40 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?