-
Notifications
You must be signed in to change notification settings - Fork 497
[CI] chore: support cuda 13.0.2 #1309
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: Teng Ma <sima.mt@alibaba-inc.com>
|
Note Gemini is unable to generate a summary for this pull request due to the file types involved not being currently supported. |
Signed-off-by: Teng Ma <sima.mt@alibaba-inc.com>
|
@UNIDY2002 I can provide some failed logs for these test cases. |
Wheels built with CUDA 13.0 may not be compatible with lower CUDA versions. |
|
Do you think it a good idea to publish separate packages, like mooncake-transfer-engine-cu12, mooncake-transfer-engine-cu13? |
How about your opinion? @ShangmingCai @ykwd It seems cu12 and cu13 are two significantly different environments. |
|
I think maybe we can build mooncake-transfer-engine-cu13 for CUDA 13, and let the original one serve CUDA 12 as it is doing now. |
| pip install torch==$version | ||
| pip install torch==$version --index-url https://download.pytorch.org/whl/cu130 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we learn how PyTorch handles this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
PyTorch essentially maintains its own registry for various CUDA versions, without depending on pypi.
Description
Type of Change
How Has This Been Tested?
Checklist