KEMBAR78
Cuda 12.1 - Remove from trunk tests by atalman · Pull Request #143076 · pytorch/pytorch · GitHub
Skip to content

Conversation

atalman
Copy link
Contributor

@atalman atalman commented Dec 11, 2024

Remove cuda 12.1 from trunk tests. This is covered by 12.4 tests.
Move libtorch-linux-focal-cuda12_4-py3_7-gcc9-debug-build -> libtorch-linux-focal-cuda12_4-py3_10-gcc9-debug-build

@atalman atalman requested a review from a team as a code owner December 11, 2024 23:04
@pytorch-bot
Copy link

pytorch-bot bot commented Dec 11, 2024

🔗 Helpful Links

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

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

✅ No Failures

As of commit 487324e with merge base 1b3f8b7 (image):
💚 Looks good so far! There are no failures yet. 💚

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

@pytorch-bot pytorch-bot bot added the topic: not user facing topic category label Dec 11, 2024
Copy link
Contributor

@huydhn huydhn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! There are too many configuration in different workflows to keep track of them all :)

@huydhn
Copy link
Contributor

huydhn commented Dec 11, 2024

cc @wdvr Here is an example of a change that will reduce CI cost from this month going forward

@atalman atalman added the ciflow/trunk Trigger trunk jobs on your pull request label Dec 11, 2024
Copy link
Contributor

@malfet malfet left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@malfet
Copy link
Contributor

malfet commented Dec 12, 2024

@pytorchbot merge -f "Trunk jobs are green for the most part"

@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

Labels

ciflow/trunk Trigger trunk jobs on your pull request Merged topic: not user facing topic category

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants