mirror of
https://github.com/deepseek-ai/DeepEP.git
synced 2026-11-05 00:47:32 +00:00
[GH-ISSUE #670] [BUG] DeepEPv2 internode num_worst_tokens tests #398
Labels
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
deepseek-ai/DeepEP#398
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @GeofferyGeng on GitHub (Jun 23, 2026).
Original GitHub issue: https://github.com/deepseek-ai/DeepEP/issues/670
Error log:
When testing DeepEP v2 internode mode with with_topk enabled, the code will assign a value to num_worst_tokens.
https://github.com/deepseek-ai/DeepEP/blob/main/tests/legacy/test_internode.py#L175
However, there is a strict assertion check inside Buffer::dispatch for multi-RDMA-rank internode scenarios:
https://github.com/deepseek-ai/DeepEP/blob/main/deep_ep/buffers/legacy.py#L378
Could we resolve the incompatibility between with_topk and internode dispatch, or add parameter pre-judgment to avoid this conflict?
@GeofferyGeng commented on GitHub (Jun 23, 2026):
Temporary fix: comment out relevant code in internode tests.
@tommy85 commented on GitHub (Aug 18, 2026):
This is fixed by #697 (the
num_worst_tokens != 0block intests/legacy/test_internode.pyis dead code copy-pasted from the intranode test — internode dispatch rejectsnum_worst_tokens > 0by design). Reproduced and verified on a 2-node × 8-GPU H20 cluster: with that block skipped, the legacy internode suite passes 32/32 sub-cases. Details in https://github.com/deepseek-ai/DeepEP/pull/697#issuecomment-5328539472