[ci] add mtp test config in pr_test#4651
Open
zhulinJulia24 wants to merge 13 commits into
Open
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
This PR updates the autotest/CI configuration to add MTP (multi-token prediction / speculative decoding) coverage to PR test matrices and per-model YAML configs.
Changes:
- Extend
PYTORCH_PR_TEST_LLM_GPU2andPYTORCH_PR_TEST_LLM_GPU1PR test run-config lists with new MTP-related entries. - Add MTP engine
extrasettings to theQwen/Qwen3.5-35B-A3Bper-model autotest YAML for thea100environment. - Introduce a new per-model autotest YAML for
internlm/Intern-S2-Preview, including MTP-related coverage entries.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| autotest/tools/common_case_config.py | Adds new PR-test run configurations, including MTP/speculative decoding parameters. |
| autotest/configs/Qwen/Qwen3.5-35B-A3B.yml | Adds a100 matrix entries that include MTP-related engine_config.extra settings. |
| autotest/configs/internlm/Intern-S2-Preview.yml | Adds a new model matrix config file with standard + MTP coverage entries. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
zhulinJulia24
force-pushed
the
add_mtp_prtest_new
branch
from
95d0e68 to
f97b32a
Compare
lvhan028
reviewed
Jun 9, 2026
Comment on lines
+45
to
+53
| - model_type: chat | ||
| engine_config: | ||
| tp: 1 | ||
| extra: | ||
| speculative-algorithm: qwen3_5_mtp | ||
| speculative-num-draft-tokens: 4 | ||
| max-batch-size: 256 | ||
| backends: | ||
| - name: turbomind |
Collaborator
There was a problem hiding this comment.
turbomind hasn't supported mtp yet.
lvhan028
reviewed
Jun 9, 2026
| # HF model id: internlm/Intern-S2-Preview | ||
|
|
||
| a100: | ||
| - model_type: chat |
Collaborator
There was a problem hiding this comment.
In the latest main branch, turbomind support intern-s2-preview's vision model.
So , we can use the following for both turbomind and pytorch engines
- model_type:
- chat
- vl
lvhan028
reviewed
Jun 9, 2026
Comment on lines
+68
to
+69
| turbomind: | ||
| - awq |
Collaborator
There was a problem hiding this comment.
This feature hasn't been merged yet.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Thanks for your contribution and we appreciate it a lot. The following instructions would make your pull request more healthy and more easily receiving feedbacks. If you do not understand some items, don't worry, just make the pull request and seek help from maintainers.
Motivation
Please describe the motivation of this PR and the goal you want to achieve through this PR.
Modification
Please briefly describe what modification is made in this PR.
BC-breaking (Optional)
Does the modification introduce changes that break the backward-compatibility of the downstream repositories?
If so, please describe how it breaks the compatibility and how the downstream projects should modify their code to keep compatibility with this PR.
Use cases (Optional)
If this PR introduces a new feature, it is better to list some use cases here, and update the documentation.
Checklist