Add CI job to run CPython tests by guilhermeleobas · Pull Request #174414 · pytorch/pytorch

guilhermeleobas · 2026-02-05T20:29:26Z

Stack from ghstack (oldest at bottom):

-> Add CI job to run CPython tests #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.

cc @voznesenskym @penguinwu @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @kadeng @chauhang @amjames @Lucaskabela @jataylo

[ghstack-poisoned]

pytorch-bot · 2026-02-05T20:29:31Z

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/174414

📄 Preview Python docs built from this PR
📄 Preview C++ docs built from this PR
❓ Need help or want to give feedback on the CI? Visit the bot commands wiki

Note: Links to docs will display an error until the docs builds have been completed.

✅ You can merge normally! (5 Unrelated Failures)

As of commit fd1a89a with merge base 659af3c ():

FLAKY - The following jobs failed but were likely due to flakiness present on trunk:

inductor / unit-test / inductor-test / test (inductor, 1, 2, linux.g5.4xlarge.nvidia.gpu) (gh) (similar failure)
test/inductor/test_torchinductor_opinfo.py::TestInductorOpInfoCUDA::test_comprehensive_pca_lowrank_cuda_float32
inductor / unit-test / inductor-test / test (inductor, 2, 2, linux.g5.4xlarge.nvidia.gpu) (gh) (similar failure)
test/inductor/test_torchinductor_opinfo.py::TestInductorOpInfoCUDA::test_comprehensive_linalg_lu_factor_cuda_float32

UNSTABLE - The following jobs are marked as unstable, possibly due to flakiness on trunk:

inductor / inductor-cpu-test / test (cpu_inductor_torchbench, 2, 2, linux.2xlarge.amx, unstable) (gh) (#174929)
pytorch_CycleGAN_and_pix2pix
inductor / inductor-test / test (inductor_torchbench, 2, 2, linux.g5.4xlarge.nvidia.gpu, unstable) (gh) (#174919)
pytorch_CycleGAN_and_pix2pix
inductor / inductor-test-cuda13 / test (inductor_torchbench, 2, 2, linux.g5.4xlarge.nvidia.gpu) (gh) (#174930)
pytorch_CycleGAN_and_pix2pix

This comment was automatically generated by Dr. CI and updates every 15 minutes.

ghstack-source-id: a71119b Pull-Request: #174414

[ghstack-poisoned]

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

[ghstack-poisoned]

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

[ghstack-poisoned]

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

[ghstack-poisoned]

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

Lucaskabela · 2026-02-05T23:14:03Z

This has my endorsement, but since it is CI related I will let devinfra folks approve (cc @atalman @seemethere)

huydhn · 2026-02-06T03:49:57Z

+name: cpython-unittest
+
+on:
+  pull_request:


Having pull_request trigger here would mean this new workflow will be run on all PyTorch PR, so I suggest we move it to pull.yml instead. That's where we expect all pull jobs to be.

This workflow only uses CPU runner linux.c7i.2xlarge, so capacity is not an issue from infra side

The test is still failing on CI though

Thanks for the review @huydhn. Is there a way to only trigger this job if one changes any code on torch/_dynamo?

[ghstack-poisoned]

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

guilhermeleobas · 2026-02-09T15:25:59Z

@pytorchbot rebase

guilhermeleobas · 2026-02-13T00:39:27Z

@pytorchbot merge -i

pytorchmergebot · 2026-02-13T00:42:26Z

Merge started

Your change will be merged while ignoring the following 9 checks: inductor / unit-test / inductor-cpu-core-build (3.11) / build, inductor / inductor-cpu-test / test (cpu_inductor_torchbench, 2, 2, linux.2xlarge.amx), inductor / unit-test / inductor-test / test (inductor, 1, 2, linux.g5.4xlarge.nvidia.gpu), inductor / inductor-test-cuda13 / test (inductor_torchbench, 2, 2, linux.g5.4xlarge.nvidia.gpu), inductor / inductor-test / test (inductor_torchbench, 2, 2, linux.g5.4xlarge.nvidia.gpu), linux-aarch64 / linux-jammy-aarch64-py3.10 / test (openreg, 1, 1, linux.arm64.m8g.4xlarge), trunk / linux-jammy-rocm-py3.10 / test (distributed, 2, 3, linux.rocm.gpu.gfx950.4), trunk / linux-jammy-cuda13.0-py3.10-gcc11 / test (distributed, 2, 3, linux.g4dn.12xlarge.nvidia.gpu), trunk / linux-jammy-cuda12.8-py3.10-gcc11 / test (distributed, 2, 3, linux.g4dn.12xlarge.nvidia.gpu)

Learn more about merging in the wiki.

Questions? Feedback? Please reach out to the PyTorch DevX Team

Advanced Debugging

Check the merge workflow status
here

seemethere · 2026-02-13T07:47:12Z

@pytorchbot revert -c nosignal -m "Looks like this is failing since it's been merged into main, https://hud.pytorch.org/pytorch/pytorch/commit/391682ea327c3ead03c23d254ee67575a24cf2f2"

pytorchmergebot · 2026-02-13T07:49:02Z

@pytorchbot successfully started a revert job. Check the current status here.
Questions? Feedback? Please reach out to the PyTorch DevX Team

This reverts commit 391682e. Reverted #174414 on behalf of https://github.com/seemethere due to Looks like this is failing since it's been merged into main, https://hud.pytorch.org/pytorch/pytorch/commit/391682ea327c3ead03c23d254ee67575a24cf2f2 ([comment](#174414 (comment)))

pytorchmergebot · 2026-02-13T07:49:11Z

@guilhermeleobas your PR has been successfully reverted.

guilhermeleobas · 2026-02-13T14:24:36Z

@pytorchbot rebase

pytorchmergebot · 2026-02-13T14:26:23Z

@pytorchbot started a rebase job onto refs/remotes/origin/viable/strict. Check the current status here

[ghstack-poisoned]

pytorchmergebot · 2026-02-13T14:26:39Z

Successfully rebased gh/guilhermeleobas/286/orig onto refs/remotes/origin/viable/strict, please pull locally before adding more changes (for example, via ghstack checkout https://github.com/pytorch/pytorch/pull/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: 67f43f6 Pull-Request: #174414

[ghstack-poisoned]

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

guilhermeleobas · 2026-02-13T17:53:22Z

@pytorchbot merge

pytorchmergebot · 2026-02-13T17:55:48Z

Merge started

Your 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

Advanced Debugging

Check the merge workflow status
here

…75034) The `dynamo-cpython-test` CI job (added in #174414) shipped with expected failure markers for `DictTest.test_values` and `DictTest.test_items`, but these tests actually pass under dynamo on Python 3.13. The test framework treats this as "unexpected success" and reports a CI failure. Authored with Claude. Pull Request resolved: #175034 Approved by: https://github.com/mlazos

Update

71ff09e

[ghstack-poisoned]

pytorch-bot Bot added the release notes: releng release notes category label Feb 5, 2026

guilhermeleobas added a commit that referenced this pull request Feb 5, 2026

Add CI job to run CPython tests

33475ab

ghstack-source-id: a71119b Pull-Request: #174414

pytorchbot added the open source label Feb 5, 2026

Update

89e7c1d

[ghstack-poisoned]

Update

01d0739

[ghstack-poisoned]

Update

63135b8

[ghstack-poisoned]

guilhermeleobas marked this pull request as ready for review February 5, 2026 20:52

guilhermeleobas requested a review from a team as a code owner February 5, 2026 20:52

guilhermeleobas requested review from Lucaskabela and malfet February 5, 2026 20:52

Update

6476a34

[ghstack-poisoned]

guilhermeleobas requested review from atalman and removed request for malfet February 5, 2026 20:57

guilhermeleobas mentioned this pull request Feb 6, 2026

Cpython test refactor fixes #174415

Closed

huydhn reviewed Feb 6, 2026

View reviewed changes

Update

8eaa5f7

[ghstack-poisoned]

pytorch-bot Bot added ciflow/inductor module: dynamo labels Feb 6, 2026

guilhermeleobas requested a review from huydhn February 7, 2026 16:47

guilhermeleobas mentioned this pull request Feb 9, 2026

[dynamo] Add cpython enum tests #174458

Closed

pytorchmergebot added the merging label Feb 13, 2026

pytorchmergebot added the Merged label Feb 13, 2026

pytorchmergebot closed this in 391682e Feb 13, 2026

pytorchmergebot removed the merging label Feb 13, 2026

pytorchmergebot added Reverted ci-no-td Do not run TD on this PR labels Feb 13, 2026

pytorchmergebot reopened this Feb 13, 2026

Update

66134fe

[ghstack-poisoned]

Update

fd1a89a

[ghstack-poisoned]

pytorchmergebot added the merging label Feb 13, 2026

pytorchmergebot closed this in 9ffb723 Feb 13, 2026

pytorchmergebot removed the merging label Feb 13, 2026

seemethere mentioned this pull request Feb 14, 2026

Remove stale dynamo cpython expected failure markers for DictTest #175034

Closed

github-actions Bot deleted the gh/guilhermeleobas/286/head branch March 16, 2026 02:25

Conversation

guilhermeleobas commented Feb 5, 2026 • edited by pytorch-bot Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

pytorch-bot Bot commented Feb 5, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/174414

✅ You can merge normally! (5 Unrelated Failures)

Uh oh!

Lucaskabela commented Feb 5, 2026

Uh oh!

huydhn Feb 6, 2026

Choose a reason for hiding this comment

Uh oh!

guilhermeleobas Feb 6, 2026

Choose a reason for hiding this comment

Uh oh!

guilhermeleobas commented Feb 9, 2026

Uh oh!

guilhermeleobas commented Feb 13, 2026

Uh oh!

pytorchmergebot commented Feb 13, 2026

Merge started

Uh oh!

seemethere commented Feb 13, 2026

Uh oh!

pytorchmergebot commented Feb 13, 2026

Uh oh!

pytorchmergebot commented Feb 13, 2026

Uh oh!

guilhermeleobas commented Feb 13, 2026

Uh oh!

pytorchmergebot commented Feb 13, 2026

Uh oh!

pytorchmergebot commented Feb 13, 2026

Uh oh!

guilhermeleobas commented Feb 13, 2026

Uh oh!

pytorchmergebot commented Feb 13, 2026

Merge started

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

6 participants

guilhermeleobas commented Feb 5, 2026 •

edited by pytorch-bot Bot

Loading

pytorch-bot Bot commented Feb 5, 2026 •

edited

Loading