Parent Log: http://ci.aztec-labs.com/182784f95254e63d Command: fb52012d377692f9 yarn-project/scripts/run_test.sh pxe/src/synchronizer/synchronizer.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/1e338a3fb2e2077f1feaee8b86c42644ff8a5352 Env: REF_NAME=gh-readonly-queue/next/pr-15075-fa4d5ef48c8de52059b5658bbd42e4514386f7db CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Mon Jun 16 16:42:26 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15075_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:42:28 [16:42:28.904] INFO: kv-store:lmdb-v2:test Starting data store with maxReaders 16 16:42:29 [16:42:29.438] INFO: kv-store:lmdb-v2:test Starting data store with maxReaders 16 16:42:30 [16:42:30.082] WARN: pxe:synchronizer Pruning data after block 3 due to reorg 16:42:30 PASS src/synchronizer/synchronizer.test.ts 16:42:30 Synchronizer 16:42:30 ✓ sets header from latest block (543 ms) 16:42:30 ✓ removes notes from db on a reorg (764 ms) 16:42:30 16:42:30 Test Suites: 1 passed, 1 total 16:42:30 Tests: 2 passed, 2 total 16:42:30 Snapshots: 0 total 16:42:30 Time: 2.88 s 16:42:30 Ran all test suites matching pxe/src/synchronizer/synchronizer.test.ts. 16:42:30 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?