[CI][1/N] Add basic ci for PD disaggregation #830
Merged
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
Yikun
force-pushed
the
pd-ci
branch
5 times, most recently
from
05c5b14 to
2e0349a
Compare
Signed-off-by: Yikun Jiang <yikunkero@gmail.com>
Yikun
added
pd-test
Yikun
changed the title
13 tasks
wangxiyuan
approved these changes
May 14, 2025
chopper0126
pushed a commit
to chopper0126/vllm-ascend
that referenced
this pull request
Oct 16, 2025
### What this PR does / why we need it? Add basic CI for PD disaggregation, and enable it when schedule and label with `module:pd` - Updated `.github/actionlint.yaml` to add a new self-hosted runner configuration: `linux-arm64-npu-static-8`. - Introduced a new GitHub Actions workflow `.github/workflows/vllm_ascend_test_pd.yaml` for PD disaggregation testing: - Scheduled to run daily at 23:00 UTC and triggered by pull request label `module:pd`. - Added steps for baisci installation and other steps will add in followup PR Related: vllm-project#841 ### Does this PR introduce _any_ user-facing change? No ### How was this patch tested? - CI passed - No trigger by default <img width="847" alt="image" src="https://github.com/user-attachments/assets/23aa128f-526d-447f-91c8-8ebf6be8400f" /> - Trigger only if we tag with pd <img width="930" alt="image" src="https://github.com/user-attachments/assets/aef1caca-2029-48e8-a6e6-860136adcd37" /> Signed-off-by: Yikun Jiang <yikunkero@gmail.com>
Angazenn
pushed a commit
to Angazenn/vllm-ascend
that referenced
this pull request
Oct 21, 2025
### What this PR does / why we need it? Add basic CI for PD disaggregation, and enable it when schedule and label with `module:pd` - Updated `.github/actionlint.yaml` to add a new self-hosted runner configuration: `linux-arm64-npu-static-8`. - Introduced a new GitHub Actions workflow `.github/workflows/vllm_ascend_test_pd.yaml` for PD disaggregation testing: - Scheduled to run daily at 23:00 UTC and triggered by pull request label `module:pd`. - Added steps for baisci installation and other steps will add in followup PR Related: vllm-project#841 ### Does this PR introduce _any_ user-facing change? No ### How was this patch tested? - CI passed - No trigger by default <img width="847" alt="image" src="https://github.com/user-attachments/assets/23aa128f-526d-447f-91c8-8ebf6be8400f" /> - Trigger only if we tag with pd <img width="930" alt="image" src="https://github.com/user-attachments/assets/aef1caca-2029-48e8-a6e6-860136adcd37" /> 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?
Add basic CI for PD disaggregation, and enable it when schedule and label with
module:pd.github/actionlint.yamlto add a new self-hosted runner configuration:linux-arm64-npu-static-8..github/workflows/vllm_ascend_test_pd.yamlfor PD disaggregation testing:module:pd.Related: #841
Does this PR introduce any user-facing change?
No
How was this patch tested?