fix: restore VLM nightly regression coverage - #34662
Merged
hnyls2002 merged 6 commits intoAug 13, 2026
Merged
Conversation
Collaborator
Author
|
/tag-run-ci-label |
mickqian
marked this pull request as ready for review
August 13, 2026 03:16
Collaborator
Author
|
/tag-and-rerun-ci |
Collaborator
Author
|
/rerun-test |
Contributor
|
⛔ Please specify a test: Examples:
|
Collaborator
|
/rerun-test test/registered/eval/test_vlms_mmmu_eval.py |
Contributor
|
Results for 🚀 |
Contributor
|
🚀 Dispatching |
Collaborator
Author
|
/rerun-test test/registered/eval/test_vlms_mmmu_eval.py |
Contributor
|
Results for 🚀 |
Collaborator
Author
|
/rerun-test test/registered/eval/test_vlms_mmmu_eval.py |
Contributor
|
Results for 🚀 |
5 tasks
saturn-acc
pushed a commit
to saturn-acc/sglang
that referenced
this pull request
Aug 16, 2026
chencjcj
pushed a commit
to chencjcj/sglang
that referenced
this pull request
Aug 17, 2026
(cherry picked from commit 69bf601)
hanwlax
pushed a commit
to hanwlax/sglang
that referenced
this pull request
Aug 28, 2026
jakki-amd
pushed a commit
to jakki-amd/sglang
that referenced
this pull request
Sep 9, 2026
Atituiset
pushed a commit
to Atituiset/sglang
that referenced
this pull request
Sep 10, 2026
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.
Summary
Root cause
PR #27327 increased the MMMU CoT generation budget from 30 to 1024 tokens, but the latency thresholds still described the old 30-token workload. Nightly results moved to a new stable latency plateau immediately after that change, so the old thresholds no longer measured engine regressions.
Pixtral's score has ranged from 0.33 to 0.37 on the fixed 100-sample suite since that change. A 0.36 floor therefore flakes on normal one- or two-question variation; this PR uses 0.32 as the regression floor.
GLM-4.5V-FP8 also had a separate real regression after single-node CUDA IPC became the default. Its fixed 1 GiB feature pool reduced the GLM nightly KV cache from 25,998 to 14,088 tokens, reducing output throughput from about 687 to 549 tokens/s and increasing latency from about 107 to 131 seconds. The latest run reached 148 seconds. Restoring CPU as the single-node default recovers the KV-cache headroom while keeping CUDA IPC available through
--mm-feature-transport=cuda_ipc.The GLM latency threshold is calibrated to the pre-regression 100-119 second plateau with headroom at 140 seconds, so a 208-second result still fails.
Validation
git diff --checkpassestransformers.image_processing_backends; Linux/H100 CI is required for runtime validationCI States
Latest PR Test (Base): ❌ Run #31668017794
Latest PR Test (Extra): ❌ Run #31668017661