Pull latest Sphinx theme

[svekars]

No description provided.

[pytorch-bot]

🔗 Helpful Links

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

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

⏳ 52 Pending, 1 Unrelated Failure

As of commit 3fd1695 with merge base 1e86fa2 ():

FLAKY - The following job failed but was likely due to flakiness present on trunk:

• docker-builds / docker-build (linux.12xlarge, pytorch-linux-jammy-py3.9-gcc11-inductor-benchmarks) (gh) (detected as infra flaky with no log or failing log classifier)

UNSTABLE - The following job is marked as unstable, possibly due to flakiness on trunk:

• ⏳ pull / cuda12.8-py3.10-gcc9-sm75 / test (pr_time_benchmarks, 1, 1, linux.g4dn.metal.nvidia.gpu, unstable) (gh) (#153987)

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

[albanD]

Sounds ok. I guess this is tested via visual inspection of the pages?

[svekars]

Sounds ok. I guess this is tested via visual inspection of the pages?

Yes, visual inspection.

[svekars]

@pytorchbot merge

[pytorchmergebot]

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

Advanced Debugging

Check the merge workflow status
here

[pytorchmergebot]

Merge failed

Reason: 1 mandatory check(s) failed. The first few are:

• pull / linux-jammy-py3-clang18-mobile-build / build

Dig deeper by viewing the failures on hud

Details for Dev Infra team

Raised by workflow job

Failing merge rule: Core Maintainers

[svekars]

@pytorchbot rebase

[pytorchmergebot]

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

[pytorchmergebot]

Successfully rebased svekars-patch-2 onto refs/remotes/origin/viable/strict, please pull locally before adding more changes (for example, via git checkout svekars-patch-2 && git pull --rebase)

[svekars]

@pytorchbot merge -f "Docs only change"

[pytorchmergebot]

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

Advanced Debugging

Check the merge workflow status
here

[svekars]

@pytorchbot cherry-pick --onto release/2.8 -c docs

[pytorchbot]

Cherry picking #158595

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

Auto-merging .ci/docker/requirements-docs.txt
CONFLICT (content): Merge conflict in .ci/docker/requirements-docs.txt
Auto-merging docs/source/conf.py
error: could not apply 79e49efaddf... Pull latest Sphinx theme (#158595)
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"

Details for Dev Infra team

Raised by workflow job