pytorch - 💡(How to fix) Fix DISABLED test_memory_plots (__main__.TestCudaAllocator) [1 comments, 1 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#179739Fetched 2026-04-09 07:50:12
View on GitHub
Comments
1
Participants
1
Timeline
30
Reactions
0
Participants
Timeline (top)
mentioned ×12subscribed ×12labeled ×4closed ×1

Root Cause

This test was disabled because it is failing in CI. See recent examples and the most recent trunk workflow logs.

RAW_BUFFERClick to expand / collapse

Platforms: linux, slow

This test was disabled because it is failing in CI. See recent examples and the most recent trunk workflow logs.

Over the past 6 hours, it has been determined flaky in 5 workflow(s) with 10 failures and 5 successes.

Debugging instructions (after clicking on the recent samples link): DO NOT ASSUME THINGS ARE OKAY IF THE CI IS GREEN. We now shield flaky tests from developers so CI will thus be green but it will be harder to parse the logs. To find relevant log snippets:

  1. Click on the workflow logs linked above
  2. Click on the Test step of the job so that it is expanded. Otherwise, the grepping will not work.
  3. Grep for test_memory_plots
  4. There should be several instances run (as flaky tests are rerun in CI) from which you can study the logs.

Test file path: test_cuda.py

For all disabled tests (by GitHub issue), see https://hud.pytorch.org/disabled.

cc @ptrblck @msaroufim @eqy @jerryzh168 @tinglvv @nWEIdia

extent analysis

TL;DR

The test test_memory_plots in test_cuda.py is failing intermittently in CI, and debugging is required to identify the root cause.

Guidance

  • To debug the issue, follow the provided instructions: click on the workflow logs, expand the Test step, and grep for test_memory_plots to find relevant log snippets.
  • Study the logs from multiple instances of the test run to identify patterns or common errors.
  • Check the test file test_cuda.py for any potential issues related to CUDA allocation or memory plots.
  • Review the list of disabled tests at https://hud.pytorch.org/disabled for any similar issues or patterns.

Example

No specific code snippet can be provided without further information, but the test file test_cuda.py should be reviewed for any potential issues.

Notes

The issue is intermittent, and the CI is green due to shielding of flaky tests, making it harder to parse the logs. The provided debugging instructions should help identify the root cause.

Recommendation

Apply workaround: Debug the test test_memory_plots in test_cuda.py by following the provided instructions to identify and fix the root cause of the intermittent failure.

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