Parent Log: http://ci.aztec-labs.com/3558fcb46aaa3f45 Command: dc9591c437eedcb5 yarn-project/scripts/run_test.sh pxe/src/synchronizer/synchronizer.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/42440bd429a3b283b3a344db0be4652d818bd261 Env: REF_NAME=gh-readonly-queue/next/pr-15046-2469b5f1633350f6be15733c04242af1cdc98227 CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Mon Jun 16 19:50:09 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15046_amd64_x3-full Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_2e465335ef4e0ed8_next 19:50:11 [19:50:11.919] INFO: kv-store:lmdb-v2:test Starting data store with maxReaders 16 19:50:12 [19:50:12.412] INFO: kv-store:lmdb-v2:test Starting data store with maxReaders 16 19:50:13 [19:50:13.065] WARN: pxe:synchronizer Pruning data after block 3 due to reorg 19:50:13 PASS src/synchronizer/synchronizer.test.ts 19:50:13 Synchronizer 19:50:13 ✓ sets header from latest block (516 ms) 19:50:13 ✓ removes notes from db on a reorg (756 ms) 19:50:13 19:50:13 Test Suites: 1 passed, 1 total 19:50:13 Tests: 2 passed, 2 total 19:50:13 Snapshots: 0 total 19:50:13 Time: 2.838 s 19:50:13 Ran all test suites matching pxe/src/synchronizer/synchronizer.test.ts. 19:50:13 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?