pytorch - 💡(How to fix) Fix DISABLED test_memory_stats_of_multiple_generators_and_graphs (__main__.TestCuda) [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#176999Fetched 2026-04-08 00:23:06
View on GitHub
Comments
1
Participants
1
Timeline
42
Reactions
0
Participants
Timeline (top)
mentioned ×18subscribed ×18labeled ×4closed ×1

Error Message

Traceback (most recent call last): File "/var/lib/jenkins/workspace/test/test_cuda.py", line 2348, in test_memory_stats_of_multiple_generators_and_graphs test(10, 20) File "/var/lib/jenkins/workspace/test/test_cuda.py", line 2339, in test self.assertEqual( File "/opt/conda/envs/py_3.10/lib/python3.10/site-packages/torch/testing/_internal/common_utils.py", line 4365, in assertEqual raise error_metas.pop()[0].to_error( # type: ignore[index] AssertionError: Scalars are not equal!

Expected 6 but got 4. Absolute difference: 2 Relative difference: 0.3333333333333333

The failure occurred for item [0] Memory stats do not match baseline after cleanup.

To execute this test, run the following from the base repo dir: python test/test_cuda.py TestCuda.test_memory_stats_of_multiple_generators_and_graphs

This message can be suppressed by setting PYTORCH_PRINT_REPRO_ON_FAILURE=0

Root Cause

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

Code Example

Traceback (most recent call last):
  File "/var/lib/jenkins/workspace/test/test_cuda.py", line 2348, in test_memory_stats_of_multiple_generators_and_graphs
    test(10, 20)
  File "/var/lib/jenkins/workspace/test/test_cuda.py", line 2339, in test
    self.assertEqual(
  File "/opt/conda/envs/py_3.10/lib/python3.10/site-packages/torch/testing/_internal/common_utils.py", line 4365, in assertEqual
    raise error_metas.pop()[0].to_error(  # type: ignore[index]
AssertionError: Scalars are not equal!

Expected 6 but got 4.
Absolute difference: 2
Relative difference: 0.3333333333333333

The failure occurred for item [0]
Memory stats do not match baseline after cleanup.

To execute this test, run the following from the base repo dir:
    python test/test_cuda.py TestCuda.test_memory_stats_of_multiple_generators_and_graphs

This message can be suppressed by setting PYTORCH_PRINT_REPRO_ON_FAILURE=0
RAW_BUFFERClick to expand / collapse

Platforms: linux

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 4 workflow(s) with 8 failures and 4 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_stats_of_multiple_generators_and_graphs
  4. There should be several instances run (as flaky tests are rerun in CI) from which you can study the logs.
<details><summary>Sample error message</summary>
Traceback (most recent call last):
  File "/var/lib/jenkins/workspace/test/test_cuda.py", line 2348, in test_memory_stats_of_multiple_generators_and_graphs
    test(10, 20)
  File "/var/lib/jenkins/workspace/test/test_cuda.py", line 2339, in test
    self.assertEqual(
  File "/opt/conda/envs/py_3.10/lib/python3.10/site-packages/torch/testing/_internal/common_utils.py", line 4365, in assertEqual
    raise error_metas.pop()[0].to_error(  # type: ignore[index]
AssertionError: Scalars are not equal!

Expected 6 but got 4.
Absolute difference: 2
Relative difference: 0.3333333333333333

The failure occurred for item [0]
Memory stats do not match baseline after cleanup.

To execute this test, run the following from the base repo dir:
    python test/test_cuda.py TestCuda.test_memory_stats_of_multiple_generators_and_graphs

This message can be suppressed by setting PYTORCH_PRINT_REPRO_ON_FAILURE=0
</details>

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

Fix Plan

Fixing Flaky Test: test_memory_stats_of_multiple_generators_and_graphs

Step 1: Identify the root cause of the flakiness

The test is failing due to an assertion error in the test_memory_stats_of_multiple_generators_and_graphs function. The error message indicates that the memory stats do not match the baseline after cleanup.

Step 2: Investigate the test code

Review the test code in test_cuda.py to understand the test logic and identify potential issues.

Step 3: Update the test code to handle flakiness

To fix the flakiness, we need to update the test code to handle the assertion error and provide more information about the failure.

import torch
import pytest

@pytest.mark.flaky(reruns=3, reruns_delay=0.5)
def test_memory_stats_of_multiple_generators_and_graphs():
    # Test logic here
    try:
        self.assertEqual(
            # expected value
            6,
            # actual value
            4
        )
    except AssertionError as e:
        # Log the failure and provide more information
        print(f"AssertionError: Scalars are not equal! Expected {6} but got {4}.")
        print(f"Absolute difference: {abs(6 - 4)}")
        print(f"Relative difference: {abs((6 - 4) / 6)}")
        # Re-raise the exception to fail the test
        raise

Step 4: Run the test with the updated code

Run the test with the updated code to verify that it passes.

Step 5: Verify the fix

Verify that the fix works by running the test multiple times and checking that it passes consistently.

Verification

To verify that the fix worked, run the test multiple times and check that it passes consistently. You can use the pytest command with the

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