Skip to content

[CI/CD] Remove CUDA 11.8 builds #155509

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.

Sign up for GitHub

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

Jump to bottom
Closed
wants to merge 5 commits into from
Closed

[CI/CD] Remove CUDA 11.8 builds #155509

wants to merge 5 commits into from

Conversation

atalman
Copy link
Contributor

@atalman atalman commented Jun 10, 2025 •
edited by pytorch-bot bot
Loading

This removes CUDA 11.8 from CI/CD
Please see: #147383

TODO: Will followup of cleaning CUDA 11.8 config from scripts

cc @albanD

@atalman atalman requested a review from a team as a code owner June 10, 2025 00:26
@pytorch-bot pytorch-bot bot added the topic: not user facing topic category label Jun 10, 2025
@pytorch-bot PyTorch Bot
Copy link

pytorch-bot bot commented Jun 10, 2025 •
edited
Loading

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/155509

Note: Links to docs will display an error until the docs builds have been completed.

❌ 2 New Failures, 22 Pending, 1 Unrelated Failure

As of commit 7d40e55 with merge base b8bc2c2 (image):

NEW FAILURES - The following jobs have failed:

UNSTABLE - The following job is marked as unstable, possibly due to flakiness on trunk:

This comment was automatically generated by Dr. CI and updates every 15 minutes.

@atalman atalman changed the title [CD] Remove CUDA 11.8 builds from nightlies [CI/CD] Remove CUDA 11.8 builds from nightlies Jun 10, 2025
@atalman atalman changed the title [CI/CD] Remove CUDA 11.8 builds from nightlies [CI/CD] Remove CUDA 11.8 builds Jun 10, 2025
@cyyever
Copy link
Collaborator

cyyever commented Jun 10, 2025

@pytorchmergebot merge -i

@pytorch-bot pytorch-bot bot added the ciflow/trunk Trigger trunk jobs on your pull request label Jun 10, 2025
@pytorchmergebot
Copy link
Collaborator

Merge started

Your change will be merged while ignoring the following 1 checks: pull / linux-jammy-py3-clang12-executorch / test (executorch, 1, 1, linux.2xlarge, unstable)

Learn more about merging in the wiki.

Questions? Feedback? Please reach out to the PyTorch DevX Team

Advanced Debugging
Check the merge workflow status
here

@cyyever
Copy link
Collaborator

cyyever commented Jun 10, 2025

@pytorchmergebot merge -f "Unrelated build failures"

@pytorchmergebot
Copy link
Collaborator

The merge job was canceled or timed out. This most often happen if two merge requests were issued for the same PR, or if merge job was waiting for more than 6 hours for tests to finish. In later case, please do not hesitate to reissue the merge command
For more information see pytorch-bot wiki.

@pytorchmergebot
Copy link
Collaborator

Merge started

Your change will be merged immediately since you used the force (-f) flag, bypassing any CI checks (ETA: 1-5 minutes). Please use -f as last resort and instead consider -i/--ignore-current to continue the merge ignoring current failures. This will allow currently pending tests to finish and report signal before the merge.

Learn more about merging in the wiki.

Questions? Feedback? Please reach out to the PyTorch DevX Team

Advanced Debugging
Check the merge workflow status
here

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@huydhn huydhn huydhn approved these changes

@malfet malfet malfet approved these changes

@cyyever cyyever cyyever approved these changes

Assignees
No one assigned
Labels
ciflow/trunk Trigger trunk jobs on your pull request Merged skip-pr-sanity-checks topic: not user facing topic category
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
5 participants
@atalman @cyyever @pytorchmergebot @huydhn @malfet