[CI] Add rocm CI back to trunk for pre-submit/PR jobs#165674
Closed
jithunnair-amd wants to merge 3 commits intopytorch:mainfrom
Closed
[CI] Add rocm CI back to trunk for pre-submit/PR jobs#165674jithunnair-amd wants to merge 3 commits intopytorch:mainfrom
jithunnair-amd wants to merge 3 commits intopytorch:mainfrom
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/165674
Note: Links to docs will display an error until the docs builds have been completed. ❗ 1 Active SEVsThere are 1 currently active SEVs. If your PR is affected, please view them below: ✅ No FailuresAs of commit 4fbdae2 with merge base d4a713c ( This comment was automatically generated by Dr. CI and updates every 15 minutes. |
pytorch-bot
bot
added
ciflow/rocm
jithunnair-amd
changed the title
jeffdaily
approved these changes
Oct 16, 2025
Collaborator
Author
|
@pytorchbot merge |
Collaborator
Merge startedYour change will be merged once all checks pass (ETA 0-4 Hours). Learn more about merging in the wiki. Questions? Feedback? Please reach out to the PyTorch DevX Team |
Chao1Han
pushed a commit
to Chao1Han/pytorch
that referenced
this pull request
Oct 21, 2025
Only adding single-GPU shards for now, to observe how current capacity handles it. Pull Request resolved: pytorch#165674 Approved by: https://github.com/jeffdaily
zhudada0120
pushed a commit
to zhudada0120/pytorch
that referenced
this pull request
Oct 22, 2025
Only adding single-GPU shards for now, to observe how current capacity handles it. Pull Request resolved: pytorch#165674 Approved by: https://github.com/jeffdaily
malfet
added a commit
that referenced
this pull request
Jan 27, 2026
They way they were added by #165674 makes signal from this jobs only visible on PR, but skipped when actually pushed to trunk, see https://hud.pytorch.org/hud/pytorch/pytorch/main/1?per_page=50&name_filter=trunk%20%2F%20linux-jammy-rocm which avoids usual latency monitoring, but creates a very confusing pattern, when `broken on trunk` status is never applied to those jobs This deficiency was highlighted in late Nov 2025, but still not fix as of late Jan 2026 as of almost ghstack-source-id: 537d31b Pull-Request: #173573
pytorchmergebot
pushed a commit
that referenced
this pull request
Jan 27, 2026
They way they were added by #165674 makes signal from this jobs only visible on PR, but skipped when actually pushed to trunk, see https://hud.pytorch.org/hud/pytorch/pytorch/main/1?per_page=50&name_filter=trunk%20%2F%20linux-jammy-rocm which avoids usual latency monitoring, but creates a very confusing pattern, when `broken on trunk` status is never applied to those jobs This deficiency was highlighted in late Nov 2025, but still not fix as of late Jan 2026 as of almost Pull Request resolved: #173573 Approved by: https://github.com/seemethere
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Only adding single-GPU shards for now, to observe how current capacity handles it.
cc @jeffdaily @sunway513 @pruthvistony @ROCmSupport @dllehr-amd @jataylo @hongxiayang @naromero77amd