pytorch - 💡(How to fix) Fix DISABLED test_raw_amdsmi_device_uuids (__main__.TestCudaAllocator) [1 comments, 2 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#180227Fetched 2026-04-15 06:19:15
View on GitHub
Comments
1
Participants
2
Timeline
28
Reactions
0
Author
Timeline (top)
mentioned ×11subscribed ×11labeled ×5commented ×1

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

extent analysis

TL;DR

The test test_raw_amdsmi_device_uuids in test_cuda.py is failing on the main branch and needs to be investigated and fixed.

Guidance

  • Review the recent failure examples on torch-ci.com to understand the failure patterns and potential causes.
  • Check the test case test_raw_amdsmi_device_uuids in test_cuda.py to see if there are any platform-specific issues or assumptions that may be causing the failure on the ROCm platform.
  • Investigate potential differences in behavior between the ROCm platform and other platforms where the test may be passing.
  • Consider re-enabling the test and running it locally or on a CI environment to gather more information about the failure.

Notes

The issue lacks specific technical details about the failure, so a more detailed analysis of the test case and the failure examples is needed to determine the root cause.

Recommendation

Apply workaround: Re-enable the test and run it locally or on a CI environment to gather more information about the failure, as the current information is not sufficient to determine a clear fix.

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