[#13819][feat] AutoDeploy: Qwen3.5 MoE (VLM) MTP - #14641
[#13819][feat] AutoDeploy: Qwen3.5 MoE (VLM) MTP#14641govind-ramnarayan wants to merge 3 commits into
Conversation
Signed-off-by: Govind Ramnarayan <105831528+govind-ramnarayan@users.noreply.github.com>
df42231 to
360c6fc
Compare
Signed-off-by: Govind Ramnarayan <105831528+govind-ramnarayan@users.noreply.github.com>
|
/bot run --stage-list "DGX_B200-8_GPUs-AutoDeploy-Post-Merge-1" |
|
PR_Github #53427 [ run ] triggered by Bot. Commit: |
Signed-off-by: Govind Ramnarayan <105831528+govind-ramnarayan@users.noreply.github.com>
|
/bot run --stage-list "DGX_B200-8_GPUs-AutoDeploy-Post-Merge-1" |
|
PR_Github #53439 [ run ] triggered by Bot. Commit: |
|
PR_Github #53427 [ run ] completed with state |
|
PR_Github #53439 [ run ] completed with state
|
|
/bot run --stage-list "DGX_B200-8_GPUs-AutoDeploy-Post-Merge-1" |
|
PR_Github #53616 [ run ] triggered by Bot. Commit: |
|
PR_Github #53616 [ run ] completed with state |
|
/bot run --disable-fail-fast |
Note: Verified that this ran the new Qwen3.5 MoE nvfp4 + mtp test and passed. Will assume this is true unless drastic changes are made to the PR and just try to get pre-merge green |
|
PR_Github #53740 [ run ] triggered by Bot. Commit: |
|
PR_Github #53740 [ run ] completed with state
|
fixes: #13819
Parts to this change:
eagle.pyand modeling code inmodeling_eagle.py, wherever we need to combine information from submodules into one (e.g. quantization configs in the factory) or split kwargs per submodule (when dispatching args to submodules in the model.forward()).And then various unit and smoke tests.
The main e2e test is a qwen 3.5 moe nvfp4 + mtp accuracy test that also checks the acceptance rate at the other end.
Summary by CodeRabbit
Release Notes
New Features
Tests
Description
Test Coverage
PR Checklist
Please review the following before submitting your PR:
PR description clearly explains what and why. If using CodeRabbit's summary, please make sure it makes sense.
PR Follows TRT-LLM CODING GUIDELINES to the best of your knowledge.
Test cases are provided for new code paths (see test instructions)
If PR introduces API changes, an appropriate PR label is added - either
api-compatibleorapi-breaking. Forapi-breaking, includeBREAKINGin the PR title.Any new dependencies have been scanned for license and vulnerabilities
CODEOWNERS updated if ownership changes
Documentation updated as needed
Update tava architecture diagram if there is a significant design change in PR.
The reviewers assigned automatically/manually are appropriate for the PR.
Please check this after reviewing the above items as appropriate for this PR.
GitHub Bot Help
To see a list of available CI bot commands, please comment
/bot help.