-
Notifications
You must be signed in to change notification settings - Fork 25.7k
[quant][pt2][ROCm] follow-up PR 109908 for miopen_batch_norm #110653
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/110653
Note: Links to docs will display an error until the docs builds have been completed. ✅ You can merge normally! (1 Unrelated Failure)As of commit d0e1825 with merge base ada6550 ( UNSTABLE - The following job failed but was likely due to flakiness present on trunk and has been marked as unstable:
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
|
@andrewor14 maybe we need to add a unittest for hip as well |
We do have CI for ROCm/HIP but at the time of the original PR it was in unstable state so was not a blocking signal. We're working on improving the CI signal response time for ROCm CI. |
|
@pytorchbot merge -f "the rocm failure is known and being addressed by separate PR but not related to this current PR" |
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 |
|
@jeffdaily Thanks for fixing this! |
Fixes recent broken unit tests caused by PR #109908 because cudnn and miopen have separate batch norm functions.
cc @sunway513 @jithunnair-amd @pruthvistony @ROCmSupport @dllehr-amd @jataylo @hongxiayang