-
Notifications
You must be signed in to change notification settings - Fork 25.7k
[CI] [ROCm] Run rocm workflow on every push to main branch #135644
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
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/135644
Note: Links to docs will display an error until the docs builds have been completed. This comment was automatically generated by Dr. CI and updates every 15 minutes. |
|
@pytorchbot merge -f 'Simple CI update, there are some numpy failures that require rebase to fix but it seems like a waste' -c weird |
|
❌ 🤖 pytorchbot command failed: Try |
|
@pytorchbot merge -f 'Simple CI update, there are some numpy failures that require rebase to fix but it seems like a waste' |
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 |
|
We should monitor the queue time for ROCM runners and if/when it exceeds say 8 hours, this PR should be reverted... |
I agree. @amdfaa Please take note. |
…35644) Dial the frequency back up from pytorch#131637 Pull Request resolved: pytorch#135644 Approved by: https://github.com/huydhn
Dial the frequency back up from #131637
cc @jeffdaily @sunway513 @pruthvistony @ROCmSupport @dllehr-amd @jataylo @hongxiayang