[ROCm] UT verifies a runtime error is raised if tensor.item() is captured in a cudagraph

[naromero77amd]

Unit test for this PR: #158165

This unit test verifies that a runtime error is raised when tensor.item() operation is captured in a cudagraph. Equally valid for ROCm and CUDA.

cc @jeffdaily @sunway513 @jithunnair-amd @pruthvistony @ROCmSupport @dllehr-amd @jataylo @hongxiayang

[pytorch-bot]

🔗 Helpful Links

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

• 📄 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, 2 Unrelated Failures

As of commit 944bc57 with merge base fd47401 ():

NEW FAILURE - The following job has failed:

• rocm / linux-jammy-rocm-py3.10 / test (default, 1, 6, linux.rocm.gpu.2) (gh)
  inductor/test_max_autotune.py::TestMaxAutotune::test_max_autotune_decompose_k_envvars_num_decompose_k_splits_20_decompose_k_threshold_16

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

• rocm / linux-jammy-rocm-py3.10 / test (default, 3, 6, linux.rocm.gpu.2) (gh) (matched linux rule in flaky-rules.json)
  The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.

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

• pull / linux-jammy-py3_9-clang9-xla / test (xla, 1, 1, lf.linux.12xlarge, unstable) (gh) (#158876)
  sccache: error: couldn't connect to server

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

[naromero77amd]

Confirming that new UT passed for CUDA in linux-jammy-cuda12.8-py3.10-gcc11 / test (default, 2, 5, lf.linux.4xlarge.nvidia.gpu)

2025-07-22T23:05:26.8088709Z test_cuda.py::TestCuda::test_cuda_graph_tensor_item_not_allowed PASSED [0.1947s] [ 10%]

[naromero77amd]

Confirming new UT passed for ROCm in linux-jammy-rocm-py3.10 / test (default, 2, 6, linux.rocm.gpu.2)

test/test_cuda.py::TestCuda::test_cuda_graph_tensor_item_not_allowed, test/test_cuda.py::TestCuda::test_cuda_memory_leak_detection_propagates_errors, test/test_cuda.py::TestCuda::test_cudart_register, 

[jeffdaily]

@pytorchbot merge -f "unrelated CI failure, new UT is passing for relevant backends"

[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