Skip to content

Conversation

Yikun
Copy link
Collaborator

@Yikun Yikun commented Sep 12, 2025

What this PR does / why we need it?

Upgrade CANN version to 8.3.rc1.alpha002

Does this PR introduce any user-facing change?

Yes, docker image are using 8.3.rc1.alpha002

How was this patch tested?

CI passed

Copy link

👋 Hi! Thank you for contributing to the vLLM Ascend project. The following points will speed up your PR merge:‌‌

  • A PR should do only one thing, smaller PRs enable faster reviews.
  • Every PR should include unit tests and end-to-end tests ‌to ensure it works and is not broken by other future PRs.
  • Write the commit message by fulfilling the PR description to help reviewer and future developers understand.

If CI fails, you can run linting and testing checks locally according Contributing and Testing.

@github-actions github-actions bot added documentation Improvements or additions to documentation ci/build labels Sep 12, 2025
Copy link

This pull request has conflicts, please resolve those before we can evaluate the pull request.

@Yikun
Copy link
Collaborator Author

Yikun commented Sep 12, 2025

test failed due to #2885

@Yikun Yikun added accuracy-test enable all accuracy test for PR ready read for review ready-for-test start test by label for PR labels Sep 12, 2025
Copy link

codecov bot commented Sep 12, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 74.89%. Comparing base (1bbb20e) to head (6a1816c).
⚠️ Report is 31 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #2880      +/-   ##
==========================================
+ Coverage   74.76%   74.89%   +0.13%     
==========================================
  Files         150      154       +4     
  Lines       20891    21243     +352     
==========================================
+ Hits        15620    15911     +291     
- Misses       5271     5332      +61     
Flag Coverage Δ
unittests 74.89% <ø> (+0.13%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@Yikun Yikun removed the ready-for-test start test by label for PR label Sep 12, 2025
@Yikun Yikun added module:tests ready-for-test start test by label for PR labels Sep 12, 2025
@Yikun Yikun added ready-for-test start test by label for PR and removed ready-for-test start test by label for PR labels Sep 12, 2025
Copy link

This pull request has conflicts, please resolve those before we can evaluate the pull request.

@github-actions github-actions bot added merge-conflicts and removed ready read for review merge-conflicts labels Sep 13, 2025
Copy link

This pull request has conflicts, please resolve those before we can evaluate the pull request.

@Yikun Yikun added ready read for review ready-for-test start test by label for PR and removed ready-for-test start test by label for PR merge-conflicts labels Sep 23, 2025
Yikun and others added 3 commits September 23, 2025 17:04
Signed-off-by: Yikun Jiang <yikunkero@gmail.com>
Signed-off-by: Yikun Jiang <yikunkero@gmail.com>
Signed-off-by: MengqingCao <cmq0113@163.com>
Copy link

This pull request has conflicts, please resolve those before we can evaluate the pull request.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
accuracy-test enable all accuracy test for PR documentation Improvements or additions to documentation merge-conflicts ready-for-test start test by label for PR
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants