Parent Log: http://ci.aztec-labs.com/d91d6842ab6606c6 Command: 2ca1986c0c6d5c2c yarn-project/scripts/run_test.sh pxe/src/synchronizer/synchronizer.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/9222c7777effe26aa04b5367a455d25be0e7f62e Env: REF_NAME=gh-readonly-queue/next/pr-15055-a9bb2f683797c8e631b892c5f539a2867bddaabf CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Wed Jun 18 16:03:30 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15055_amd64_x4-full Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_2e465335ef4e0ed8_next 16:03:32 [16:03:32.519] INFO: kv-store:lmdb-v2:test Starting data store with maxReaders 16 16:03:32 [16:03:32.980] INFO: kv-store:lmdb-v2:test Starting data store with maxReaders 16 16:03:33 [16:03:33.614] WARN: pxe:synchronizer Pruning data after block 3 due to reorg 16:03:33 PASS src/synchronizer/synchronizer.test.ts 16:03:33 Synchronizer 16:03:33 ✓ sets header from latest block (469 ms) 16:03:33 ✓ removes notes from db on a reorg (779 ms) 16:03:33 16:03:33 Test Suites: 1 passed, 1 total 16:03:33 Tests: 2 passed, 2 total 16:03:33 Snapshots: 0 total 16:03:33 Time: 2.721 s 16:03:33 Ran all test suites matching pxe/src/synchronizer/synchronizer.test.ts. 16:03:33 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?