Issue Station
Sign In
Tools hereToolbox

pytorch - 💡(How to fix) Fix DISABLED test_uuid_visible_devices (__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#180123•Fetched 2026-04-12 13:23:56
View on GitHub
Comments
1
Participants
2
Timeline
29
Reactions
0
Author
jithunnair-amdjithunnair-amd
Participants
jithunnair-amdjithunnair-amdpytorch-bot[bot]pytorch-bot[bot]
Timeline (top)
mentioned ×11subscribed ×11labeled ×6commented ×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 @pruthvistony @ROCmSupport @jataylo @hongxiayang @naromero77amd @pragupta @jerrymannil @xinyazhang @mruberry

extent analysis

TL;DR

The test test_cuda_expandable_segments.py needs to be re-enabled and fixed to resolve the failure on the main branch.

Guidance

  • Investigate the recent examples of test failures on torch-ci.com to understand the nature of the failure.
  • Review the test test_cuda_expandable_segments.py and the TestCudaAllocator class to identify potential issues with the test or the allocator.
  • Consider re-enabling the test and running it locally to reproduce and debug the failure.
  • Check if there are any known issues or fixes related to the ROCm platform that could be contributing to the test failure.

Notes

The exact cause of the test failure is not specified, and more information would be needed to provide a definitive fix.

Recommendation

Apply workaround: Re-enable the test and debug it locally to identify the root cause of the failure, as the issue seems to be specific to the test and the ROCm platform.

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…
#training loop#device allocation#model download#tokenizer error#prompt formatting

Still need to ship something?

×6

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

Back to top recommendations

TRENDING