test(e2e): add Qwen3 MoE CUDA coverage - #241
Conversation
Signed-off-by: Xinpei Wang <wangxinpei@tju.edu.cn>
7dcbb95 to
ad493ca
Compare
|
@yujuancao07 Please help review this. |
hsliuustc0106
left a comment
There was a problem hiding this comment.
[P2] Use Qwen node IDs in the run-e2e command
At .agents/skills/run-e2e/SKILL.md:101-102, the instruction says to replace only the test path in the preceding command. That command still contains ::test_deepseek_v2_lite[...]; after replacing the path, pytest cannot collect the Qwen cases because the new function is test_qwen3_moe. Please provide a complete Qwen command, such as python -m pytest -q -s tests/e2e/models/qwen3_moe/test_qwen3_moe.py, or list the four Qwen node IDs.
Validation: full tests/unit passed; the Qwen model unit tests passed under vLLM 0.26; Ruff and compile checks passed. CPU-only CI is green; GPU/NPU E2E was not run locally.
Signed-off-by: Xinpei Wang <wangxinpei@tju.edu.cn>
The Qwen3 section now provides a complete pytest command. |
Purpose
Add repository-owned CUDA E2E coverage for Qwen3 MoE after #216, following the E2E contract introduced by #222 and refined by #238.
Changes
baseline-graph,afd-eager,afd-graph, andafd-graph-dbo.run-e2eskill for the Qwen3 MoE suite.The production code, shared E2E runner, CI configuration, and DeepSeek-V2-Lite scenario behavior are unchanged.
Validation
pre-commit run --files ...python -m pytest -q tests/unit: 571 passed, 46 skippedCoordination
Rebased onto
mainafter #238.Related to #215, #216, #222, and #238.