Skip to content

fix: make TORCH_LOGS tutorial work without CUDA 7.0+#3910

Open
TheChyeahhh wants to merge 1 commit into
pytorch:mainfrom
TheChyeahhh:fix/torch-logs-cpu-compat
Open

fix: make TORCH_LOGS tutorial work without CUDA 7.0+#3910
TheChyeahhh wants to merge 1 commit into
pytorch:mainfrom
TheChyeahhh:fix/torch-logs-cpu-compat

Conversation

@TheChyeahhh
Copy link
Copy Markdown

Summary

The TORCH_LOGS tutorial at recipes/torch_logs.html had an early-exit guard that skipped all tutorial code when no CUDA device with compute capability >= 7.0 was found. The rendered docs showed only

Skipping because torch.compile is not supported on this device.

instead of the actual logging output the tutorial is meant to demonstrate.

Changes

  • Changed the guard from a hard skip to a graceful CPU fallback when no suitable GPU is available
  • Prints an informational message so readers understand the fallback
  • All logging sections now execute regardless of GPU availability

Test Plan

  • Build on CPU-only CI shard: GALLERY_PATTERN="torch_logs.py" make html
  • Build on GPU-enabled CI shard (existing behavior preserved)

Closes #137285

The tutorial had a guard that skipped all code when no CUDA device with
compute capability >= 7.0 was available, causing the rendered docs to
only show the skip message instead of actual logging output.

Changed the guard to fall back to CPU tensors with the CPU inductor
backend when no suitable GPU is found. This allows the tutorial to
produce meaningful output regardless of the CI build environment.

Fixes #137285
@pytorch-bot
Copy link
Copy Markdown

pytorch-bot Bot commented May 29, 2026

🔗 Helpful Links

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

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:

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

@meta-cla
Copy link
Copy Markdown

meta-cla Bot commented May 29, 2026

Hi @TheChyeahhh!

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 added the cla signed label May 29, 2026
@meta-cla
Copy link
Copy Markdown

meta-cla Bot commented May 29, 2026

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

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.

1 participant