Fix CPython 3.13 test failures reported in dynamo-unittest job#172448
Fix CPython 3.13 test failures reported in dynamo-unittest job#172448guilhermeleobas wants to merge 9 commits intogh/guilhermeleobas/276/basefrom
Conversation
| finally: | ||
| _converting.discard(self_id) | ||
|
|
||
| def is_python_constant(self): |
There was a problem hiding this comment.
nit: add -> bool: to function def and should be good
Lucaskabela
left a comment
There was a problem hiding this comment.
Minor typing nit (pyrefly signal is blocking). Should be a straightforward fix - thanks for fixing these tests!
| def is_python_constant(self) -> bool: | ||
| try: | ||
| self.as_python_constant() | ||
| return True | ||
| except Exception: | ||
| return False | ||
|
|
There was a problem hiding this comment.
@tugsbayasgalan could you see if this change makes sense to you? _get_function() is called from as_python_constant() and if tx.output.side_effects.load_cell(cell_var) raises unsupported, Dynamo bail and skips all remaining frames. This is problematic for the CPython test suite as some tests will suddenly pass.
There was a problem hiding this comment.
Quick reminder that this changes the default impl. of is_python_constant to capture any Exception and not just NotImplementedError.
There was a problem hiding this comment.
Do we just need to catch ClosureConversionError as well?
There was a problem hiding this comment.
Yes! No, Unsupported.
|
@pytorchbot merge |
Merge startedYour change will be merged once all checks pass (ETA 0-4 Hours). Learn more about merging in the wiki. Questions? Feedback? Please reach out to the PyTorch DevX Team |
Merge failedReason: 9 jobs have failed, first few of them are: trunk / linux-jammy-rocm-py3.10 / test (default, 2, 6, linux.rocm.gpu.gfx942.1), trunk / linux-jammy-rocm-py3.10 / test (default, 6, 6, linux.rocm.gpu.gfx942.1), trunk / linux-jammy-rocm-py3.10 / test (default, 4, 6, linux.rocm.gpu.gfx942.1), trunk / linux-jammy-rocm-py3.10 / test (distributed, 1, 3, linux.rocm.gpu.gfx942.4), trunk / linux-jammy-rocm-py3.10 / test (default, 1, 6, linux.rocm.gpu.gfx942.1) Details for Dev Infra teamRaised by workflow job |
|
@pytorchbot merge |
Merge startedYour change will be merged once all checks pass (ETA 0-4 Hours). Learn more about merging in the wiki. Questions? Feedback? Please reach out to the PyTorch DevX Team |
Merge failedReason: 9 jobs have failed, first few of them are: trunk / linux-jammy-rocm-py3.10 / test (default, 2, 6, linux.rocm.gpu.gfx942.1), trunk / linux-jammy-rocm-py3.10 / test (default, 6, 6, linux.rocm.gpu.gfx942.1), trunk / linux-jammy-rocm-py3.10 / test (default, 4, 6, linux.rocm.gpu.gfx942.1), trunk / linux-jammy-rocm-py3.10 / test (distributed, 1, 3, linux.rocm.gpu.gfx942.4), trunk / linux-jammy-rocm-py3.10 / test (default, 1, 6, linux.rocm.gpu.gfx942.1) Details for Dev Infra teamRaised by workflow job |
|
@pytorchbot merge -i |
The dynamo-unnitest (Python 3.13) job is constantly failing due to some CPython tests starts passing or failing. In the past, I've send PRs (#174091, #172448) to make the job green again but it is a matter of days for it to start failing again. This PR adds a CI job that only runs the CPython tests on Python 3.13 to ensure we catch these errors earlier on. ghstack-source-id: 8d53b96 Pull-Request: #174414
The dynamo-unnitest (Python 3.13) job is constantly failing due to some CPython tests starts passing or failing. In the past, I've send PRs (#174091, #172448) to make the job green again but it is a matter of days for it to start failing again. This PR adds a dedicated Ci job that runs only the CPython tests on Python 3.13, allowing us to catch these issues earlier. ghstack-source-id: 8d53b96 Pull-Request: #174414
The dynamo-unnitest (Python 3.13) job is constantly failing due to some CPython tests starts passing or failing. In the past, I've send PRs (#174091, #172448) to make the job green again but it is a matter of days for it to start failing again. This PR adds a dedicated Ci job that runs only the CPython tests on Python 3.13, allowing us to catch these issues earlier. ghstack-source-id: 9e4183b Pull-Request: #174414
The dynamo-unnitest (Python 3.13) job is constantly failing due to some CPython tests starts passing or failing. In the past, I've send PRs (#174091, #172448) to make the job green again but it is a matter of days for it to start failing again. This PR adds a dedicated Ci job that runs only the CPython tests on Python 3.13, allowing us to catch these issues earlier. Contrary to this one, the dynamo-unittest job runs weekly on a broader set of tests. This one is supposed to run on pull requests that touches dynamo. ghstack-source-id: 4b1e42d Pull-Request: #174414
The dynamo-unnitest (Python 3.13) job is constantly failing due to some CPython tests starts passing or failing. In the past, I've send PRs (#174091, #172448) to make the job green again but it is a matter of days for it to start failing again. This PR adds a dedicated Ci job that runs only the CPython tests on Python 3.13, allowing us to catch these issues earlier. Contrary to this one, the dynamo-unittest job runs weekly on a broader set of tests. This one is supposed to run on pull requests that touches dynamo. ghstack-source-id: 6ecd6a3 Pull-Request: #174414
The dynamo-unnitest (Python 3.13) job is constantly failing due to some CPython tests starts passing or failing. In the past, I've send PRs (#174091, #172448) to make the job green again but it is a matter of days for it to start failing again. This PR adds a dedicated Ci job that runs only the CPython tests on Python 3.13, allowing us to catch these issues earlier. Contrary to this one, the dynamo-unittest job runs weekly on a broader set of tests. This one is supposed to run on pull requests that touches dynamo. ghstack-source-id: 3db6709 Pull-Request: #174414
The dynamo-unnitest (Python 3.13) job is constantly failing due to some CPython tests starts passing or failing. In the past, I've send PRs (#174091, #172448) to make the job green again but it is a matter of days for it to start failing again. This PR adds a dedicated Ci job that runs only the CPython tests on Python 3.13, allowing us to catch these issues earlier. Contrary to this one, the dynamo-unittest job runs weekly on a broader set of tests. This one is supposed to run on pull requests that touches dynamo. ghstack-source-id: 1c3b41d Pull-Request: #174414
The dynamo-unnitest (Python 3.13) job is constantly failing due to some CPython tests starts passing or failing. In the past, I've send PRs (#174091, #172448) to make the job green again but it is a matter of days for it to start failing again. This PR adds a dedicated Ci job that runs only the CPython tests on Python 3.13, allowing us to catch these issues earlier. Contrary to this one, the dynamo-unittest job runs weekly on a broader set of tests. This one is supposed to run on pull requests that touches dynamo. ghstack-source-id: 6915a1e Pull-Request: #174414
The dynamo-unnitest (Python 3.13) job is constantly failing due to some CPython tests starts passing or failing. In the past, I've send PRs (#174091, #172448) to make the job green again but it is a matter of days for it to start failing again. This PR adds a dedicated Ci job that runs only the CPython tests on Python 3.13, allowing us to catch these issues earlier. Contrary to this one, the dynamo-unittest job runs weekly on a broader set of tests. This one is supposed to run on pull requests that touches dynamo. Pull Request resolved: #174414 Approved by: https://github.com/huydhn
The dynamo-unnitest (Python 3.13) job is constantly failing due to some CPython tests starts passing or failing. In the past, I've send PRs (#174091, #172448) to make the job green again but it is a matter of days for it to start failing again. This PR adds a dedicated Ci job that runs only the CPython tests on Python 3.13, allowing us to catch these issues earlier. Contrary to this one, the dynamo-unittest job runs weekly on a broader set of tests. This one is supposed to run on pull requests that touches dynamo. ghstack-source-id: 67f43f6 Pull-Request: #174414
The dynamo-unnitest (Python 3.13) job is constantly failing due to some CPython tests starts passing or failing. In the past, I've send PRs (#174091, #172448) to make the job green again but it is a matter of days for it to start failing again. This PR adds a dedicated Ci job that runs only the CPython tests on Python 3.13, allowing us to catch these issues earlier. Contrary to this one, the dynamo-unittest job runs weekly on a broader set of tests. This one is supposed to run on pull requests that touches dynamo. ghstack-source-id: ec908f9 Pull-Request: #174414
The dynamo-unnitest (Python 3.13) job is constantly failing due to some CPython tests starts passing or failing. In the past, I've send PRs (#174091, #172448) to make the job green again but it is a matter of days for it to start failing again. This PR adds a dedicated Ci job that runs only the CPython tests on Python 3.13, allowing us to catch these issues earlier. Contrary to this one, the dynamo-unittest job runs weekly on a broader set of tests. This one is supposed to run on pull requests that touches dynamo. Pull Request resolved: #174414 Approved by: https://github.com/huydhn
Stack from ghstack (oldest at bottom):
cc @voznesenskym @penguinwu @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @kadeng @chauhang @amjames @Lucaskabela @jataylo