pytorch - 💡(How to fix) Fix DISABLED test_dynamic_lstm_strict (__main__.StrictExportTestExport) [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#180556Fetched 2026-04-17 08:26:24
View on GitHub
Comments
1
Participants
1
Timeline
19
Reactions
0
Participants
Timeline (top)
mentioned ×7subscribed ×7labeled ×4commented ×1

Error Message

Traceback (most recent call last): File "/var/lib/jenkins/workspace/test/export/test_export.py", line 1216, in test_dynamic_lstm self.assertEqual(eager_out, ep_out) File "/opt/conda/envs/py_3.10/lib/python3.10/site-packages/torch/_dynamo/test_case.py", line 117, 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 4445, in assertEqual raise error_metas.pop()[0].to_error( # type: ignore[index] AssertionError: Tensor-likes are not close!

Mismatched elements: 22 / 262144 (0.0%) Greatest absolute difference: 2.6635825634002686e-05 at index (0, 0, 494) (up to 1e-05 allowed) Greatest relative difference: 0.0015868250047788024 at index (0, 0, 466) (up to 1.3e-06 allowed)

To execute this test, run the following from the base repo dir: PYTORCH_TEST_WITH_ASAN=1 PYTORCH_TEST_WITH_UBSAN=1 python test/export/test_export_strict.py StrictExportTestExport.test_dynamic_lstm_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 1216, in test_dynamic_lstm
    self.assertEqual(eager_out, ep_out)
  File "/opt/conda/envs/py_3.10/lib/python3.10/site-packages/torch/_dynamo/test_case.py", line 117, 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 4445, in assertEqual
    raise error_metas.pop()[0].to_error(  # type: ignore[index]
AssertionError: Tensor-likes are not close!

Mismatched elements: 22 / 262144 (0.0%)
Greatest absolute difference: 2.6635825634002686e-05 at index (0, 0, 494) (up to 1e-05 allowed)
Greatest relative difference: 0.0015868250047788024 at index (0, 0, 466) (up to 1.3e-06 allowed)

To execute this test, run the following from the base repo dir:
    PYTORCH_TEST_WITH_ASAN=1 PYTORCH_TEST_WITH_UBSAN=1 python test/export/test_export_strict.py StrictExportTestExport.test_dynamic_lstm_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_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 1216, in test_dynamic_lstm
    self.assertEqual(eager_out, ep_out)
  File "/opt/conda/envs/py_3.10/lib/python3.10/site-packages/torch/_dynamo/test_case.py", line 117, 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 4445, in assertEqual
    raise error_metas.pop()[0].to_error(  # type: ignore[index]
AssertionError: Tensor-likes are not close!

Mismatched elements: 22 / 262144 (0.0%)
Greatest absolute difference: 2.6635825634002686e-05 at index (0, 0, 494) (up to 1e-05 allowed)
Greatest relative difference: 0.0015868250047788024 at index (0, 0, 466) (up to 1.3e-06 allowed)

To execute this test, run the following from the base repo dir:
    PYTORCH_TEST_WITH_ASAN=1 PYTORCH_TEST_WITH_UBSAN=1 python test/export/test_export_strict.py StrictExportTestExport.test_dynamic_lstm_strict

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

Test file path: export/test_export_strict.py

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

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

extent analysis

TL;DR

The most likely fix involves investigating and addressing the numerical instability or precision issues in the test_dynamic_lstm_strict test, potentially by adjusting tolerance values or improving the numerical stability of the LSTM implementation.

Guidance

  • Investigate the test_dynamic_lstm_strict test in export/test_export_strict.py to understand the numerical instability causing the AssertionError: Tensor-likes are not close! error.
  • Review the logs from the workflow runs to identify patterns or common factors contributing to the test failures.
  • Consider adjusting the tolerance values for absolute and relative differences in the assertEqual method to accommodate the observed numerical instability.
  • Examine the LSTM implementation for potential improvements to numerical stability, such as using more robust numerical methods or increasing the precision of intermediate calculations.

Example

No specific code snippet is provided, as the issue requires a deeper investigation into the numerical stability of the LSTM implementation.

Notes

The fix may involve a combination of adjusting tolerance values, improving numerical stability, and potentially modifying the test to better handle numerical instability.

Recommendation

Apply a workaround by adjusting the tolerance values in the assertEqual method to temporarily mitigate the issue, while also investigating the root cause of the numerical instability.

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_strict (__main__.StrictExportTestExport) [1 comments, 1 participants]