[Build] Move numba/quart to requirments and update DS baseline and sync graph typo fix #1121
Conversation
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
Signed-off-by: Yikun Jiang <yikunkero@gmail.com>
Yikun
added
ready
|
It's ready when all CI passed |
Signed-off-by: Yikun Jiang <yikunkero@gmail.com>
Yikun
changed the title
Yikun
added
ready-for-test
Yikun
changed the title
Yikun
added
ready-for-test
wangxiyuan
approved these changes
Jun 8, 2025
Yikun
commented
Jun 8, 2025
| entry.aclgraph = aclgraph | ||
|
|
||
| compilation_counter.num_cudagraph_caputured += 1 | ||
| compilation_counter.num_cudagraph_captured += 1 |
| num_piecewise_capturable_graphs_seen=3, # 1 + num_layers | ||
| num_backend_compilations=3, # num_piecewise_capturable_graphs_seen | ||
| num_cudagraph_caputured= | ||
| num_cudagraph_captured= |
Yikun
force-pushed
the
fix-numba
branch
2 times, most recently
from
c786501 to
a18d381
Compare
Signed-off-by: Yikun Jiang <yikunkero@gmail.com>
wangxiyuan
approved these changes
Jun 8, 2025
chopper0126
pushed a commit
to chopper0126/vllm-ascend
that referenced
this pull request
Oct 16, 2025
…nc graph typo fix (vllm-project#1121) ### What this PR does / why we need it? 1. The dependency was introduced by vllm-project#874 - Move numba/quart from requirements-dev to requirments - Align pyproject.toml with requirements 2. This patch also fix deepseek accuracy baseline which vllm-project#1118 was not addressed. According to https://huggingface.co/deepseek-ai/DeepSeek-V2-Lite the gsm8k is about `41.1` 3. This also sync the vLLM upstream changes: vllm-project/vllm@eaa2e51 ### Does this PR introduce _any_ user-facing change? No ### How was this patch tested? CI passed vllm ascend test (basic workflow) vllm longterm test (spec decode) Closes: vllm-project#1120 --------- Signed-off-by: Yikun Jiang <yikunkero@gmail.com>
Angazenn
pushed a commit
to Angazenn/vllm-ascend
that referenced
this pull request
Oct 21, 2025
…nc graph typo fix (vllm-project#1121) ### What this PR does / why we need it? 1. The dependency was introduced by vllm-project#874 - Move numba/quart from requirements-dev to requirments - Align pyproject.toml with requirements 2. This patch also fix deepseek accuracy baseline which vllm-project#1118 was not addressed. According to https://huggingface.co/deepseek-ai/DeepSeek-V2-Lite the gsm8k is about `41.1` 3. This also sync the vLLM upstream changes: vllm-project/vllm@eaa2e51 ### Does this PR introduce _any_ user-facing change? No ### How was this patch tested? CI passed vllm ascend test (basic workflow) vllm longterm test (spec decode) Closes: vllm-project#1120 --------- Signed-off-by: Yikun Jiang <yikunkero@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
What this PR does / why we need it?
This patch also fix deepseek accuracy baseline which [bugfix] fix deeepseek accuracy #1118 was not addressed. According to https://huggingface.co/deepseek-ai/DeepSeek-V2-Lite the gsm8k is about
41.1This also sync the vLLM upstream changes: vllm-project/vllm@eaa2e51
Does this PR introduce any user-facing change?
No
How was this patch tested?
CI passed
vllm ascend test (basic workflow)
vllm longterm test (spec decode)
Closes: #1120