pytorch - 💡(How to fix) Fix DISABLED test_dynamic_lstm_retraceability_strict (__main__.RetraceExportTestExport) [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#176998Fetched 2026-04-08 00:23:10
View on GitHub
Comments
1
Participants
1
Timeline
49
Reactions
0
Participants
Timeline (top)
mentioned ×22subscribed ×22labeled ×4commented ×1

Error Message

Traceback (most recent call last): File "/var/lib/jenkins/workspace/test/export/test_export.py", line 1334, in test_dynamic_lstm self.assertEqual(eager_out_gru, ep_out_gru) File "/opt/conda/envs/py_3.10/lib/python3.10/site-packages/torch/_dynamo/test_case.py", line 113, in assertEqual return super().assertEqual(x, y, *args, **kwargs) 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: Tensor-likes are not close!

Mismatched elements: 597 / 262144 (0.2%) Greatest absolute difference: 3.4332275390625e-05 at index (0, 5, 240) (up to 1e-05 allowed) Greatest relative difference: 0.49453550577163696 at index (2, 6, 293) (up to 1.3e-06 allowed)

To execute this test, run the following from the base repo dir: python test/export/test_retraceability.py RetraceExportTestExport.test_dynamic_lstm_retraceability_strict

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/export/test_export.py", line 1334, in test_dynamic_lstm
    self.assertEqual(eager_out_gru, ep_out_gru)
  File "/opt/conda/envs/py_3.10/lib/python3.10/site-packages/torch/_dynamo/test_case.py", line 113, in assertEqual
    return super().assertEqual(x, y, *args, **kwargs)
  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: Tensor-likes are not close!

Mismatched elements: 597 / 262144 (0.2%)
Greatest absolute difference: 3.4332275390625e-05 at index (0, 5, 240) (up to 1e-05 allowed)
Greatest relative difference: 0.49453550577163696 at index (2, 6, 293) (up to 1.3e-06 allowed)

To execute this test, run the following from the base repo dir:
    python test/export/test_retraceability.py RetraceExportTestExport.test_dynamic_lstm_retraceability_strict

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

Platforms: asan, 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 3 workflow(s) with 3 failures and 3 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_dynamic_lstm_retraceability_strict
  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/export/test_export.py", line 1334, in test_dynamic_lstm
    self.assertEqual(eager_out_gru, ep_out_gru)
  File "/opt/conda/envs/py_3.10/lib/python3.10/site-packages/torch/_dynamo/test_case.py", line 113, in assertEqual
    return super().assertEqual(x, y, *args, **kwargs)
  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: Tensor-likes are not close!

Mismatched elements: 597 / 262144 (0.2%)
Greatest absolute difference: 3.4332275390625e-05 at index (0, 5, 240) (up to 1e-05 allowed)
Greatest relative difference: 0.49453550577163696 at index (2, 6, 293) (up to 1.3e-06 allowed)

To execute this test, run the following from the base repo dir:
    python test/export/test_retraceability.py RetraceExportTestExport.test_dynamic_lstm_retraceability_strict

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

Test file path: export/test_retraceability.py

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

cc @chauhang @penguinwu @avikchaudhuri @zhxchen17 @tugsbayasgalan @angelayi @suo @ydwu4

extent analysis

Fix Plan

1. Identify the root cause of the flaky test

The test test_dynamic_lstm_retraceability_strict is failing intermittently due to a mismatch between the expected and actual output of the torch.testing._internal.common_utils.assertEqual function.

2. Update the test to handle floating-point precision issues

To fix this issue, we can update the test to use a more relaxed tolerance when comparing floating-point numbers. We can use the torch.testing.assert_close function instead of torch.testing._internal.common_utils.assertEqual.

3. Update the test code

import torch

def test_dynamic_lstm_retraceability_strict(self):
    # ...
    torch.testing.assert_close(eager_out_gru, ep_out_gru, atol=1e-5, rtol=1e-6)
    # ...

4. Run the test again to verify the fix

Run the test again using the updated code to verify that the issue is resolved.

5. Consider adding a workaround for the flaky test

If the test is still flaky after updating the code, consider adding a workaround to skip the test or retry it multiple times. For example:

import random

def test_dynamic_lstm_retraceability_strict(self):
    if random.random() < 0.1:  # 10% chance of skipping the test
        pytest.skip("Skipping flaky test")
    # ...

6. Monitor the test results to ensure the fix is effective

Monitor the test results to ensure that the fix is effective and the test is no longer flaky.

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

pytorch - 💡(How to fix) Fix DISABLED test_dynamic_lstm_retraceability_strict (__main__.RetraceExportTestExport) [1 comments, 1 participants]