Add Ascend NPU CI workflow for backend tests#1072
Add Ascend NPU CI workflow for backend tests#1072xuedinge233 wants to merge 3 commits intolinkedin:mainfrom
Conversation
.github/workflows/ascend_npu_ci.yml
Outdated
| uv pip install attrs==24.2.0 numpy==1.26.4 scipy==1.13.1 decorator==5.1.1 psutil==6.0.0 pytest==9.0.2 pytest-xdist==3.6.1 pyyaml pybind11 transformers==4.57.6 | ||
| uv pip install torch==2.6.0 torchvision==0.21.0 torchaudio==2.6.0 --index-url https://download.pytorch.org/whl/cpu | ||
| uv pip install torch_npu==2.6.0 | ||
| uv pip install triton-ascend==3.2.0rc4 |
There was a problem hiding this comment.
triton-ascend has released its stable version. I recommend we switch to it: https://gitcode.com/Ascend/triton-ascend/releases/v3.2.0
There was a problem hiding this comment.
torch_npu and triton-ascend should be installed via uv pip install -e .[dev]. Is there any considerations why we designate specific versions?
Lines 27 to 28 in effb776
There was a problem hiding this comment.
triton-ascendhas released its stable version. I recommend we switch to it: https://gitcode.com/Ascend/triton-ascend/releases/v3.2.0
After testing, triton-ascend v3.2.0 can be completed normally. I will modify it to this version.
There was a problem hiding this comment.
torch_npuandtriton-ascendshould be installed viauv pip install -e .[dev]. Is there any considerations why we designate specific versions?Lines 27 to 28 in effb776
Currently, triton-ascend is based on torch_npu v2.6.0. If there are any subsequent updates, it will be synchronized
There was a problem hiding this comment.
Currently, triton-ascend is based on torch_npu v2.6.0. If there are any subsequent updates, it will be synchronized
Perhaps we could consider merging this PR first: #1055
3 participants
Summary
This PR introduces a new GitHub Actions workflow to validate the Ascend NPU backend using a dedicated CI pipeline.
The workflow is designed to run on Ascend NPU self-hosted runners and focuses on executing backend-related tests to ensure correctness and stability of NPU-specific implementations.
What’s included
Ascend NPU CI workflow triggered on:
push/pull_requesttomain(scoped to Ascend backend and test changes)workflow_dispatchtests job running on Ascend NPU runners with:
torch_npuandtriton-ascendAt this stage, the workflow runs the transformers test subset only. The full
make testtarget is intentionally left commented out and can be enabled incrementally once the CI setup is fully validated and stable.Motivation
The goal of this workflow is to provide early signal and continuous validation for Ascend NPU backend changes, while keeping the initial CI scope focused and reliable.
By starting with a targeted test suite, we can:
Future work
make testtarget once the CI pipeline has proven stable over time