pytorch - 💡(How to fix) Fix DISABLED test_graph_rng_after_failed_capture (__main__.TestCuda) [2 comments, 3 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
pytorch/pytorch#180222Fetched 2026-04-15 06:19:12
View on GitHub
Comments
2
Participants
3
Timeline
60
Reactions
0
Author
Timeline (top)
mentioned ×25subscribed ×25labeled ×7commented ×2

Root Cause

Platforms: rocm This test was disabled because it is failing on main branch (recent examples).

RAW_BUFFERClick to expand / collapse

Platforms: rocm This test was disabled because it is failing on main branch (recent examples).

cc @jeffdaily @sunway513 @jithunnair-amd @pruthvistony @ROCmSupport @jataylo @hongxiayang @naromero77amd @jerrymannil @xinyazhang @mruberry @pbelevich @mcarilli @ezyang @eellison @penguinwu @BoyuanFeng

extent analysis

TL;DR

  • Re-enable and re-run the disabled test test_graph_rng_after_failed_capture in test_cuda.py to assess the current failure status.

Guidance

  • Review the recent failure examples on torch-ci.com to understand the failure patterns and potential causes.
  • Investigate the test test_graph_rng_after_failed_capture in test_cuda.py to identify the root cause of the failure, considering the ROCm platform specifics.
  • Consider reaching out to the listed maintainers and experts for additional guidance and support, given their expertise in ROCm and CUDA-related issues.

Notes

  • The issue seems to be specific to the ROCm platform, so any solution or workaround might need to consider the unique characteristics and limitations of this platform.
  • Without more detailed information about the failure, such as error messages or stack traces, it's challenging to provide a more specific fix or workaround.

Recommendation

  • Apply workaround: Given the lack of detailed information, it's safer to apply a workaround, such as modifying the test to accommodate the ROCm platform specifics or temporarily skipping the test until a more permanent fix can be implemented.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING