Update docstring to match code.

[jjh42]

Very tiny fix to doc string. Pass grid_size=None results in an Exception.

[pytorch-bot]

🔗 Helpful Links

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

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

❌ 1 New Failure, 3 Unrelated Failures

As of commit 1f5a7b4 with merge base 67937be ():

NEW FAILURE - The following job has failed:

• linux-binary-manywheel / manywheel-py3_9-cuda12_8-test / test (gh)
  RuntimeError: cuDNN version incompatibility: PyTorch was compiled against (9, 8, 0) but found runtime version (9, 7, 1). PyTorch already comes bundled with cuDNN. One option to resolving this error is to ensure PyTorch can find the bundled cuDNN. one possibility is that there is a conflicting cuDNN in LD_LIBRARY_PATH.

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

• trunk / macos-py3-arm64 / test (default, 2, 3, macos-m1-stable) (gh) (similar failure)
  dynamo/test_graph_deduplication.py::GraphDededuplicationTests::test_dependent_subgraphs

BROKEN TRUNK - The following jobs failed but was present on the merge base:

👉 Rebase onto the `viable/strict` branch to avoid these failures

• trunk / libtorch-linux-focal-cuda12.4-py3.10-gcc9-debug / build (gh) (trunk failure)
  undefined reference to std::__throw_bad_array_new_length()'`
• trunk / macos-py3-arm64 / test (default, 1, 3, macos-m1-stable) (gh) (trunk failure)
  higher_order_ops/test_invoke_subgraph.py::TestInvokeSubgraphCompile::test_bwd_partitioning

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

[linux-foundation-easycla]

• ✅login: jjh42 / (1f5a7b4)

The committers listed above are authorized under a signed CLA.

[jjh42]

@pytorchbot label "topic: not user facing"

[jjh42]

Any update on this?

[mikaylagawarecki]

@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 jobs have failed, first few of them are: linux-binary-manywheel / manywheel-py3_9-cuda12_8-test / test

Details for Dev Infra team

Raised by workflow job

[jjh42]

thanks for the approval. As this PR is purely a comment/doc change it can't be the cause of the failing tests? Can you advise? Should I rebase this PR?

[jjh42]

bump?

[cyyever]

@pytorchbot merge -f "Simple fix"

[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