[Bugfix][SM70] Enable Qwen3.8 AWQ in dual-compile lane - #487
Merged
yangzhuxinyzx merged 2 commits intoSep 5, 2026
Merged
Conversation
Allow the text-only Qwen4Exp conditional-generation wrapper to use the existing shared-weight prefill/decode compilation contract while keeping full multimodal models rejected. Co-authored-by: OpenAI Codex <codex@openai.com> Signed-off-by: Leonccaa <166551845+Leonccaa@users.noreply.github.com>
Signed-off-by: Leonccaa <166551845+Leonccaa@users.noreply.github.com>
This was referenced Sep 4, 2026
Contributor
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.
Purpose
Follow up on #477 by admitting the Qwen3.8 AWQ text-only runtime to the
existing SM70 dual-compile lane.
The checkpoint keeps the outer
Qwen4ExpForConditionalGenerationarchitecture even when it is loaded with
--language-model-only, while the#477 contract admitted only
Qwen4ExpForCausalLM. This change also accepts theconditional-generation wrapper, but only when
multimodal_config.language_model_onlyis explicitly true. Full multimodalloading and a missing multimodal config remain rejected.
Real TP4 validation then exposed a second late-binding issue. #477 enables
hybrid PLE from
VllmConfig.__post_init__, afterParallelConfigvalidationwould normally allocate the shared PLE IPC endpoint. As a result, all workers
attempted to connect to an empty address and failed with
zmq.error.ZMQError: Invalid argument (addr='').This PR makes PLE endpoint initialization idempotent and invokes it when the
model-aware defaults enable PLE late. Explicit PLE configuration retains the
same behavior.
There are no AWQ kernel, quantization-math, weight-format, or scheduler
changes. Operator capability checks and existing fallbacks remain in place.
In particular, this PR does not address mixed-phase latency from chunked
prefill scheduling.
Test Plan
activations, KV auto, MTP0, prefix caching off, and
FULL_AND_PIECEWISEcompilation without explicitly setting the PLE envs.timestamps, 320 requested output tokens, and
ignore_eos=false.as an integration check.
Test Result
.venv/bin/pytest -q --confcutdir=tests/compile tests/compile/test_sm70_decode_graph.py:7 passed.
formatting, mypy, SPDX, configuration validation, and forbidden-import
checks.
workers reproduced the empty-address ZMQ failure.
arm completed startup. All four workers used the same non-empty IPC endpoint,
PLE registered 4/4 workers, and the service built the large prefill graph plus
decode capture sizes
[1, 8].returned 320 tokens with
finish_reason=length; no traceback, OOM, orruntime worker exit was observed.
21.24 -> 20.24 GiB/rankand KV capacity386,392 -> 505,574tokens(
+30.85%) versus the matched post-[Core][SM70] Split Qwen3.8 prefill and decode compilation #477 main-only arm.main-only and 2.719 s on the four-PR stack. That scheduler behavior remains
separate follow-up work.
AI assistance disclosure: OpenAI Codex assisted with implementation, test
execution, runtime evidence collation, and PR preparation. The submitter
reviewed the changes and validation results.
Essential Elements of an Effective PR Description Checklist