vllm-project/vllm-ascend

[Contribution] 任务 #10：[Ext] 高风险路径测试覆盖补强

Open

#14,151 opened on Aug 13, 2026

View on GitHubContributor guide
 (2 comments) (0 reactions) (0 assignees)C++ (2,048 forks)github user discovery
help wanted

Repository metrics

Stars
 (2,637 stars)
PR merge metrics
 (Avg merge 4d 5h) (559 merged PRs in 30d)

Description

背景

tests/ut/distributed/ascend_store/ 下已有 test_config_data.py / test_pool_worker.py / test_pool_scheduler.py / test_kv_transfer.py / test_coordinator.py 等，但对高风险路径的覆盖仍不均衡。异常路径、GVA 批量元数据、multi-group 失败恢复、异步 load/save 状态机仍需补强。

待补强路径与期望场景：

  • KVCacheTransferThread.run 线程异常分支：线程内 I/O 异常是否被正确捕获、是否传播到主流程、是否被静默吞掉
  • _alloc_gvas_for_save / _prepare_load_gvas GVA 元数据批量：批量分配的部分失败回滚、group_block_hashes 边界（空 / 单 / 满）
  • LookupKeyClient.lookup 及 ZMQ lookup server：server 无响应 / 连接断开 / 超长 payload 的编解码异常
  • layerwise _handle_request 同步等待与失败传播：gate.wait 超时、load 失败后 attention 是否被错误放行、失败标记是否一致

相关代码路径：vllm_ascend/distributed/kv_transfer/kv_pool/ascend_store。

任务

优先补"会卡死、会吞错、会错标完成"的高风险路径测试，而不是只补纯逻辑函数的 happy path。

  • 范围：上述高风险路径
  • 目标：异常注入 / 并发 / 失败传播的针对性测试覆盖

验收标准

1. 功能正确性

  • 新增测试不改变生产行为
  • 现有测试全绿

2. 覆盖指标

  • 上述高风险路径有针对性测试（异常注入 / 并发 / 失败传播）
  • 覆盖率报告显示相关路径覆盖提升

3. 交付件

  • PR + 新增测试文件 + 覆盖率对比

环境约定

  • vllm-ascend：最新 main
  • 硬件：Ascend NPU（注明型号 + 卡数 + TP/CP/PP 配置）
  • 关联任务池：#9079
  • 验收人：@赵鹏博

重点关注

  • 建议尽早落地，为后续重构提供安全网

任务周期

  • 发布：2026-08-12
  • 回收：2026-09-30

Contributor guide

Research direction
Run existing tests in tests/ut/distributed/ascend store/, then inspect source files in vllm ascend/distributed/kv transfer/kv pool/ascend store to identify untested branches. Use mocking to simulate exceptions, timeouts, and concurrent access. Check how thread exceptions are handled and write focused tests.
Tech stack
python
Domain
backenddistributed systems
Issue type
Test
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitPythonpytest
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40