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

Traceback (most recent call last): File "/var/lib/jenkins/workspace/test/dynamo/test_modes.py", line 119, in test_torch_dispatch_ignore_compile_internals self.assertEqual(counters["frames"]["total"], 1) ~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/conda/envs/py_3.14/lib/python3.14/site-packages/torch/_dynamo/test_case.py", line 113, in assertEqual return super().assertEqual(x, y, *args, **kwargs) ~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/conda/envs/py_3.14/lib/python3.14/site-packages/torch/testing/_internal/common_utils.py", line 4440, in assertEqual raise error_metas.pop()[0].to_error( # type: ignore[index] ...<4 lines>... ) AssertionError: Scalars are not equal!

Expected 1 but got 2. Absolute difference: 1 Relative difference: 1.0

To execute this test, run the following from the base repo dir: python test/dynamo/test_modes.py TorchDispatchModeTests.test_torch_dispatch_ignore_compile_internals

This message can be suppressed by setting PYTORCH_PRINT_REPRO_ON_FAILURE=0

TL;DR

The test test_torch_dispatch_ignore_compile_internals is failing intermittently due to an assertion error, and the fix likely involves investigating and resolving the discrepancy in the expected and actual values of counters["frames"]["total"].

Guidance

• Investigate the test case test_torch_dispatch_ignore_compile_internals in dynamo/test_modes.py to understand why counters["frames"]["total"] is expected to be 1 but is actually 2.
• Review the workflow logs linked in the issue to identify patterns or commonalities among the failed test runs.
• Run the test locally using the provided command python test/dynamo/test_modes.py TorchDispatchModeTests.test_torch_dispatch_ignore_compile_internals to reproduce and debug the issue.
• Consider setting PYTORCH_PRINT_REPRO_ON_FAILURE=0 to suppress the error message and focus on debugging the test failure.

Notes

The intermittent nature of the test failure and the lack of clear error patterns in the provided logs suggest that the issue may be related to the test environment or the specific conditions under which the test is run.

Recommendation

Apply workaround: Investigate and debug the test case to identify the root cause of the assertion error, as the issue is likely specific to the test environment or implementation.