🔗 Helpful Links

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

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

There are 1 currently active SEVs. If your PR is affected, please view them below:

• B200 runners offline

⏳ No Failures, 90 Pending

As of commit 6fb0f08 with merge base 3a7db34 ():
💚 Looks good so far! There are no failures yet. 💚

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

@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 mandatory check(s) failed. The first few are:

• Lint / lintrunner-noclang / linux-job

Dig deeper by viewing the failures on hud

@pytorchbot merge -f "Run lint locally, but not entirely sure if it'll be green"

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 cherry-pick --onto release/2.9 --c critical --fixes #161167

Cherry picking #162310

Command git -C /home/runner/work/pytorch/pytorch cherry-pick -x 5e7be988003a38be49227cfaa9bff6a2ea9e6929 returned non-zero exit code 1

Auto-merging .ci/docker/build.sh
Auto-merging .github/workflows/docker-builds.yml
CONFLICT (content): Merge conflict in .github/workflows/docker-builds.yml
Auto-merging .github/workflows/lint.yml
Auto-merging pyproject.toml
Auto-merging setup.py
error: could not apply 5e7be988003... [BE] Update Python min version to 3.10 (#162310)
hint: After resolving the conflicts, mark them with
hint: "git add/rm <pathspec>", then run
hint: "git cherry-pick --continue".
hint: You can instead skip this commit with "git cherry-pick --skip".
hint: To abort and get back to the state before "git cherry-pick",
hint: run "git cherry-pick --abort".
hint: Disable this message with "git config set advice.mergeConflict false"

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 cherry-pick --onto release/2.9 -c critical

Cherry picking #162310

Command git -C /home/runner/work/pytorch/pytorch cherry-pick -x 5e7be988003a38be49227cfaa9bff6a2ea9e6929 returned non-zero exit code 1

Auto-merging .ci/docker/build.sh
Auto-merging .github/workflows/docker-builds.yml
CONFLICT (content): Merge conflict in .github/workflows/docker-builds.yml
Auto-merging .github/workflows/lint.yml
Auto-merging pyproject.toml
Auto-merging setup.py
error: could not apply 5e7be988003... [BE] Update Python min version to 3.10 (#162310)
hint: After resolving the conflicts, mark them with
hint: "git add/rm <pathspec>", then run
hint: "git cherry-pick --continue".
hint: You can instead skip this commit with "git cherry-pick --skip".
hint: To abort and get back to the state before "git cherry-pick",
hint: run "git cherry-pick --abort".
hint: Disable this message with "git config set advice.mergeConflict false"