🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/117822

• 📄 Preview Python docs built from this PR
• 📄 Preview C++ docs built from this PR
• ❓ Need help or want to give feedback on the CI? Visit the bot commands wiki or our office hours

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 9c449fb with merge base fdae936 ():

This comment was automatically generated by Dr. CI and updates every 15 minutes.

@jianyuh has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.

Rebase to the trunk?

Rebase to the trunk?

This PR depends on #115214 but it got reverted due to breaking the internal build. It's in the process of relanding.

@jianyuh has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.

@pytorchbot rebase

@pytorchbot started a rebase job onto refs/remotes/origin/viable/strict. Check the current status here

Rebase failed due to Command git -C /home/runner/work/pytorch/pytorch rebase refs/remotes/origin/viable/strict pull/117822/head returned non-zero exit code 1

Rebasing (1/1)
Auto-merging aten/src/ATen/cuda/CUDADataType.h
CONFLICT (content): Merge conflict in aten/src/ATen/cuda/CUDADataType.h
error: could not apply ddc20913ac7... [ROCm] enable scaled_gemm
hint: Resolve all conflicts manually, mark them as resolved with
hint: "git add/rm <conflicted_files>", then run "git rebase --continue".
hint: You can instead skip this commit: run "git rebase --skip".
hint: To abort and get back to the state before "git rebase", run "git rebase --abort".
Could not apply ddc20913ac7... [ROCm] enable scaled_gemm

Raised by https://github.com/pytorch/pytorch/actions/runs/7616139952

Manual rebase after #115214 relanded.

@jianyuh has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.

Hi @jeffdaily , could you rebase to the trunk? There is a conflict with master so we couldn't import it internally and test the PR. Thanks!

Hi @jeffdaily , could you rebase to the trunk? There is a conflict with master so we couldn't import it internally and test the PR. Thanks!

Done.

@jianyuh has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.

@jianyuh has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.

@pytorchbot rebase

@pytorchbot started a rebase job onto refs/remotes/origin/viable/strict. Check the current status here

@pytorchbot merge

Merge failed

Reason: This PR needs a release notes: label
If your changes are user facing and intended to be a part of release notes, please use a label starting with release notes:.

If not, please add the topic: not user facing label.

To add a label, you can comment to pytorchbot, for example
@pytorchbot label "topic: not user facing"

For more information, see
https://github.com/pytorch/pytorch/wiki/PyTorch-AutoLabel-Bot#why-categorize-for-release-notes-and-how-does-it-work.

@pytorchbot label "topic: not user facing"

@pytorchbot merge

Merge started

Your 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

Merge failed

Reason: 4 jobs have failed, first few of them are: trunk, linux-binary-manywheel, linux-binary-libtorch-cxx11-abi, linux-binary-libtorch-pre-cxx11

@jeffdaily maybe fix the unit test given the merge has failed :)

@jeffdaily maybe fix the unit test given the merge has failed :)

@xw285cornell Pushed commit to resolve the unit tests. You'll need to redo your import to resolve the Meta Internal-Only Changes Check that is now failing due to my new commit push.

@jianyuh has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.

@pytorchbot merge

Merge started

Your 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

Merge failed

Reason: 1 jobs have failed, first few of them are: trunk / win-vs2019-cpu-py3 / test (default, 1, 3, windows.4xlarge.nonephemeral)

@pytorchbot merge

Merge started

Your 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

@jeffdaily is there a recommended way to detect that the rocm gpu is "ROCm MI300+"?

@jeffdaily is there a recommended way to detect that the rocm gpu is "ROCm MI300+"?

In torch C++, we have if (at::detail::getCUDAHooks().isGPUArch({"gfx942"})).

In torch python, we have if "gfx94" in torch.cuda.get_device_properties(0).gcnArchName.split(":")[0].