🔗 Helpful Links

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

• 📄 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

Note: Links to docs will display an error until the docs builds have been completed.

❌ 1 New Failure, 3 Unrelated Failures

As of commit 92ae60a with merge base 823edb4 ():

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

The committers listed above are authorized under a signed CLA.

• ✅ login: chinmaydk99 / name: Chinmay Dattanand Kuchinad (0083df7, 6763a58, 92ae60a, bc735f4, c9b9191, d5f0503, f4940df)

To add the ciflow label ciflow/inductor please first approve the workflows that are awaiting approval (scroll to the bottom of this page).

This helps ensure we don't trigger CI on this PR until it is actually authorized to do so. Please ping one of the reviewers if you do not have access to approve and run workflows.

To add the ciflow label ciflow/rocm please first approve the workflows that are awaiting approval (scroll to the bottom of this page).

This helps ensure we don't trigger CI on this PR until it is actually authorized to do so. Please ping one of the reviewers if you do not have access to approve and run workflows.

To add the ciflow label ciflow/inductor-rocm please first approve the workflows that are awaiting approval (scroll to the bottom of this page).

This helps ensure we don't trigger CI on this PR until it is actually authorized to do so. Please ping one of the reviewers if you do not have access to approve and run workflows.

Merge failed

Reason: 11 jobs have failed, first few of them are: pull / linux-jammy-py3.14-clang12 / test (default, 3, 5, lf.linux.4xlarge), pull / linux-jammy-py3.10-clang12 / test (default, 5, 5, lf.linux.4xlarge), pull / linux-jammy-py3.10-gcc11 / test (default, 4, 5, lf.linux.2xlarge), pull / linux-jammy-py3.10-clang18-asan / test (default, 3, 7, lf.linux.4xlarge), rocm-mi300 / linux-noble-rocm-py3.12-mi300 / test (default, 1, 6, linux.rocm.gpu.gfx942.1.b)

@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/166492/head returned non-zero exit code 1

Rebasing (1/6)
Auto-merging torch/_inductor/runtime/static_cuda_launcher.py
CONFLICT (content): Merge conflict in torch/_inductor/runtime/static_cuda_launcher.py
Auto-merging torch/_inductor/runtime/triton_heuristics.py
Auto-merging torch/csrc/inductor/static_cuda_launcher.cpp
error: could not apply 700c9a8e466... Enabling StaticCudaLauncher for ROCm
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".
hint: Disable this message with "git config set advice.mergeConflict false"
Could not apply 700c9a8e466... # Enabling StaticCudaLauncher for ROCm

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

@pytorchbot merge -f "only failures were flaky or broken trunk; meta internal diff also failed but we have approval to land anyway"

Merge started

Your change will be merged immediately since you used the force (-f) flag, bypassing any CI checks (ETA: 1-5 minutes). Please use -f as last resort and instead consider -i/--ignore-current to continue the merge ignoring current failures. This will allow currently pending tests to finish and report signal before the merge.

Learn more about merging in the wiki.

Questions? Feedback? Please reach out to the PyTorch DevX Team

@pytorchbot revert -m "sorry, a previous commit introduce the new test file breaks internal system, please rebase after #169121 's revert and reland" -c ghfirst

@pytorchbot successfully started a revert job. Check the current status here.
Questions? Feedback? Please reach out to the PyTorch DevX Team

@chinmaydk99 your PR has been successfully reverted.

@pytorchbot merge -f "linter infra error, other failures are known flaky"

Merge started

Your change will be merged immediately since you used the force (-f) flag, bypassing any CI checks (ETA: 1-5 minutes). Please use -f as last resort and instead consider -i/--ignore-current to continue the merge ignoring current failures. This will allow currently pending tests to finish and report signal before the merge.

Learn more about merging in the wiki.

Questions? Feedback? Please reach out to the PyTorch DevX Team

Merge failed

Reason: PR #166492 has not been reviewed yet

@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 push -f https://github.com/chinmaydk99/pytorch.git pull/166492/head:ck-staticudalauncher returned non-zero exit code 128

remote: The 'AMD' enterprise forbids access via a personal access tokens (classic) if the token's lifetime is greater than 366 days. Please adjust your token's lifetime at the following URL: https://github.com/settings/tokens/779664343
fatal: unable to access 'https://github.com/chinmaydk99/pytorch.git/': The requested URL returned error: 403

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

@pytorchbot merge -i

This PR needs to be approved by an authorized maintainer before merge.

@pytorchbot merge -i

Merge started

Your change will be merged while ignoring the following 5 checks: pull / linux-jammy-py3.14t-clang15 / test (dynamo_wrapped, 1, 3, linux.2xlarge), rocm-mi300 / linux-noble-rocm-py3.12-mi300 / test (default, 2, 6, linux.rocm.gpu.gfx942.1), inductor / inductor-test-cuda13 / test (inductor_torchbench, 2, 2, linux.g5.4xlarge.nvidia.gpu), rocm-mi200 / linux-jammy-rocm-py3.10 / test (default, 1, 6, linux.rocm.gpu.2), Meta Internal-Only Changes Check

Learn more about merging in the wiki.

Questions? Feedback? Please reach out to the PyTorch DevX Team

The merge job was canceled or timed out. This most often happen if two merge requests were issued for the same PR, or if merge job was waiting for more than 6 hours for tests to finish. In later case, please do not hesitate to reissue the merge command
For more information see pytorch-bot wiki.

@pytorchbot merge -f "Dr CI unrelated failures; lint good"

Merge started

Your change will be merged immediately since you used the force (-f) flag, bypassing any CI checks (ETA: 1-5 minutes). Please use -f as last resort and instead consider -i/--ignore-current to continue the merge ignoring current failures. This will allow currently pending tests to finish and report signal before the merge.

Learn more about merging in the wiki.

Questions? Feedback? Please reach out to the PyTorch DevX Team