Enable inductor-rocm workflow for all trunk commits AND inductor-related PRs#138623
Enable inductor-rocm workflow for all trunk commits AND inductor-related PRs#138623jithunnair-amd wants to merge 6 commits intopytorch:mainfrom
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/138623
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: ❌ 2 New FailuresAs of commit c8bda27 with merge base 2dab4cc ( NEW FAILURES - The following jobs have failed:
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
|
Tested that commit triggered inductor-rocm |
|
@pytorchbot merge -f "Fixed lint space, otherwise CI ran as expected pre-lint change" |
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 |
|
@pytorchbot revert -m 'I think the link failure is legit, it complains about the wrong concurrency setting in the workflow' -c ignoredsignal https://github.com/pytorch/pytorch/actions/runs/11745317737/job/32722467379#step:14:183 |
|
@pytorchbot successfully started a revert job. Check the current status here. |
…tor-related PRs (#138623)" This reverts commit ee7c3db. Reverted #138623 on behalf of https://github.com/huydhn due to I think the link failure is legit, it complains about the wrong concurrency setting in the workflow ([comment](#138623 (comment)))
|
@jithunnair-amd your PR has been successfully reverted. |
|
Fix worked as per: https://github.com/pytorch/pytorch/actions/runs/11962833666/job/33352070792#step:14:187 @pytorchbot merge -f "Fixed lint concurrency group naming" |
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 |
…ted PRs (pytorch#138623) It should help with triaging ROCm-inductor-related breakages and surfacing them in the PRs itself. Pull Request resolved: pytorch#138623 Approved by: https://github.com/huydhn
…tor-related PRs (pytorch#138623)" This reverts commit ee7c3db. Reverted pytorch#138623 on behalf of https://github.com/huydhn due to I think the link failure is legit, it complains about the wrong concurrency setting in the workflow ([comment](pytorch#138623 (comment)))
…ted PRs (pytorch#138623) It should help with triaging ROCm-inductor-related breakages and surfacing them in the PRs itself. Pull Request resolved: pytorch#138623 Approved by: https://github.com/huydhn
It should help with triaging ROCm-inductor-related breakages and surfacing them in the PRs itself.
cc @jeffdaily @sunway513 @pruthvistony @ROCmSupport @dllehr-amd @jataylo @hongxiayang @naromero77amd @voznesenskym @penguinwu @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @ipiszy @yf225 @chenyang78 @kadeng @muchulee8 @ColinPeppler @amjames @desertfire @chauhang @aakhundov