Parent Log: http://ci.aztec-labs.com/8251982aad1ef834 Command: a5511b51e55ea9c0 yarn-project/scripts/run_test.sh pxe/src/synchronizer/synchronizer.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/9cbd161a1dfa928167c1f969200b95df55ed4c6b Env: REF_NAME=gh-readonly-queue/next/pr-15157-6e3848bbd6845559b55825f0bc64df0673272969 CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Fri Jun 20 09:43:14 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15157_amd64_x2-full Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_2e465335ef4e0ed8_next 09:43:17 [09:43:17.537] INFO: kv-store:lmdb-v2:test Starting data store with maxReaders 16 09:43:18 [09:43:18.037] INFO: kv-store:lmdb-v2:test Starting data store with maxReaders 16 09:43:18 [09:43:18.591] WARN: pxe:synchronizer Pruning data after block 3 due to reorg 09:43:18 PASS src/synchronizer/synchronizer.test.ts 09:43:18 Synchronizer 09:43:18 ✓ sets header from latest block (524 ms) 09:43:18 ✓ removes notes from db on a reorg (663 ms) 09:43:18 09:43:18 Test Suites: 1 passed, 1 total 09:43:18 Tests: 2 passed, 2 total 09:43:18 Snapshots: 0 total 09:43:18 Time: 2.791 s 09:43:18 Ran all test suites matching pxe/src/synchronizer/synchronizer.test.ts. 09:43:18 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?