Skip to content

Fix torch_logs tutorial to run on CPU when CUDA unavailable - #3950

Open
ajaykesarwani wants to merge 1 commit into
pytorch:mainfrom
ajaykesarwani:fix/issue-137285-torch-logs-docs
Open

Fix torch_logs tutorial to run on CPU when CUDA unavailable#3950
ajaykesarwani wants to merge 1 commit into
pytorch:mainfrom
ajaykesarwani:fix/issue-137285-torch-logs-docs

Conversation

@ajaykesarwani

Copy link
Copy Markdown

Fixes pytorch/pytorch#137285

The torch_logs tutorial was skipping execution on machines without a
modern CUDA GPU (including the Sphinx doc build server), resulting in
"Skipping because torch.compile is not supported on this device."
being shown in the documentation instead of actual log output.

Changes:

  • Removed the hard torch.cuda.get_device_capability() check
  • Added device = "cuda" if torch.cuda.is_available() else "cpu" fallback
  • Fixed indentation of code that was inside the old else: block
  • Updated the .. note:: to mention that CUDA is recommended but not required

@pytorch-bot

pytorch-bot Bot commented Aug 9, 2026

Copy link
Copy Markdown

🔗 Helpful Links

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

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

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

@meta-cla

meta-cla Bot commented Aug 9, 2026

Copy link
Copy Markdown

Hi @ajaykesarwani!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks!

@meta-cla

meta-cla Bot commented Aug 9, 2026

Copy link
Copy Markdown

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks!

@meta-cla meta-cla Bot added the cla signed label Aug 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Docs are little bit outdated for torch logs

1 participant