[ROCm][CI] Change rocm periodic workflow label to linux.rocm.gpu.mi250.4#164616
Closed
amdfaa wants to merge 1 commit intopytorch:mainfrom
Closed
[ROCm][CI] Change rocm periodic workflow label to linux.rocm.gpu.mi250.4#164616amdfaa wants to merge 1 commit intopytorch:mainfrom
amdfaa wants to merge 1 commit intopytorch:mainfrom
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/164616
Note: Links to docs will display an error until the docs builds have been completed. ✅ No FailuresAs of commit 654b9b1 with merge base 1894082 ( This comment was automatically generated by Dr. CI and updates every 15 minutes. |
amdfaa
changed the title
jeffdaily
approved these changes
Oct 3, 2025
huydhn
approved these changes
Oct 3, 2025
Collaborator
|
@pytorchbot merge -f "rocm workflow runner label change" |
Collaborator
Merge startedYour change will be merged immediately since you used the force (-f) flag, bypassing any CI checks (ETA: 1-5 minutes). Please use 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
…0.4 (pytorch#164616) Testing done on this PR: pytorch#156491 Pull Request resolved: pytorch#164616 Approved by: https://github.com/jeffdaily, https://github.com/huydhn
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
5 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.
Testing done on this PR: #156491
New label
linux.rocm.gpu.mi250.4uses K8s-based ARC runners.From "Job Duration (all branches)" table on metrics.pytorch.org:
231 jobs per month * 3H (per job) * 3 shards = 2079H per month / 30 days = 69.3H per day / 3H for periodic job = ~23 Runners (assuming all jobs are run simultaneously) = 12 nodes
69.3H for jobs per day automatically assumes we are not running in parallel. If you divide this value by the time for each job then you get the max concurrent number of runners (23 i.e 12 nodes) you would have to handle the average job load per day. However, since all those jobs are usually not concurrently running, we started with 5 nodes (ie. 10 runners) with this label.
cc @jeffdaily @sunway513 @jithunnair-amd @pruthvistony @ROCmSupport @dllehr-amd @jataylo @hongxiayang @naromero77amd