Skip to content
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

Add build triggers for 2.6-rc1 #8485

Merged
merged 1 commit into from
Dec 12, 2024
Merged

Add build triggers for 2.6-rc1 #8485

merged 1 commit into from
Dec 12, 2024

Conversation

tengyifei
Copy link
Collaborator

This is modeled off of #7978. Changes from that 2.5 PR are:

  • Add C++11 ABI builds in addition to pre-C++11 ABI builds
  • Update CUDA version to 12.1 and 12.4 as per [RFC] Cuda support matrix for Release 2.6 pytorch#138609. The PyTorch RFC also mentions 11.8 but we already dropped 11.8 since 2.5 and it was marked as a legacy option so I did not include that.

Note that PyTorch has not created the v2.6.0-rc1 tag and neither have we. These triggers won't run unless the tag is created. If they did run then they'll fail and we can still re-trigger.

This is modeled off of #7978.
Changes from that 2.5 PR are:

- Add C++11 ABI builds in addition to pre-C++11 ABI builds
- Update CUDA version to 12.1 and 12.4 as per
  pytorch/pytorch#138609. The PyTorch RFC also
  mentions 11.8 but we already dropped 11.8 since 2.5 and it was marked
  as a legacy option so I did not include that.

Note that PyTorch has not created the v2.6.0-rc1 tag and neither have
we. These triggers won't run unless the tag is created. If they did run
then they'll fail and we can still re-trigger.
@tengyifei tengyifei marked this pull request as ready for review December 11, 2024 23:33
@lsy323 lsy323 merged commit 8e37d50 into master Dec 12, 2024
12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants