🔗 Helpful Links

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

• 📄 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 or our office hours

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

❌ 22 New Failures, 4 Unrelated Failures

As of commit 6b8d641 with merge base e8b1409 ():

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

The CI builds have been running smoothly with no errors so far, which is great! I wish an expert could take a look to ensure that simpy version 1.13.3 has been thoroughly tested and that the tests are sufficient to resolve the failures encountered in version 1.13.2. Unfortunately, I am unable to do so at the moment due to my limited knowledge of the build system and the repro of the original test failures.

Please seek CI approval before scheduling CIFlow labels

@pytorchbot rebase

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

Successfully rebased simpy_pinning onto refs/remotes/origin/viable/strict, please pull locally before adding more changes (for example, via git checkout simpy_pinning && git pull --rebase)

Some CI jobs failed with the following errors:

INFO: pip is looking at multiple versions of torch to determine which version is compatible with other requirements. This could take a while.
ERROR: Could not find a version that satisfies the requirement sympy>=1.13.3; python_version >= "3.9" (from torch) (from versions: 1.10.1, 1.11.1, 1.12, 1.12.1, 1.13.1)
ERROR: No matching distribution found for sympy>=1.13.3; python_version >= "3.9"

I am unsure why PyPI cannot find version 1.13.3 when it is available (https://pypi.org/project/sympy/1.13.3/). Perhaps there is a cache that needs to be updated?

Merge started

Your change will be merged while ignoring the following 4 checks: windows-binary-wheel / wheel-py3_9-xpu-build, windows-binary-wheel / wheel-py3_10-xpu-build, windows-binary-wheel / wheel-py3_11-xpu-build, windows-binary-wheel / wheel-py3_12-xpu-build

Learn more about merging in the wiki.

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

Merge failed

Reason: 5 jobs have failed, first few of them are: linux-binary-manywheel / manywheel-py3_12-xpu-build / build, linux-binary-manywheel / manywheel-py3_13-xpu-build / build, linux-binary-manywheel / manywheel-py3_11-xpu-build / build, linux-binary-manywheel / manywheel-py3_10-xpu-build / build, linux-binary-manywheel / manywheel-py3_9-xpu-build / build

@pytorchbot merge -i

Merge started

Your change will be merged while ignoring the following 10 checks: windows-binary-wheel / wheel-py3_9-xpu-build, windows-binary-wheel / wheel-py3_10-xpu-build, windows-binary-wheel / wheel-py3_11-xpu-build, windows-binary-wheel / wheel-py3_12-xpu-build, linux-binary-manywheel / manywheel-py3_12-xpu-build / build, linux-binary-manywheel / manywheel-py3_13-xpu-build / build, linux-binary-manywheel / manywheel-py3_11-xpu-build / build, linux-binary-manywheel / manywheel-py3_10-xpu-build / build, linux-binary-manywheel / manywheel-py3_9-xpu-build / build, trunk / macos-py3-arm64 / test (default, 2, 3, macos-m1-stable)

Learn more about merging in the wiki.

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

@pytorchbot revert -m 'Sorry for reverting your change, but I think a bunch of inductor tests and test_dynamic_shapes are failing in trunk after this lands https://hud.pytorch.org/pytorch/pytorch/commit/d8279ad9d162b5ce71699f462d3664c3745b14f5' -c ignoredsignal

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

@jeongseok-meta your PR has been successfully reverted.

FYI, we should also update the dependencies in lintrunner.toml (used type checking).

Removing 2.5.1 milestone, @Skylion007 why do you think it's important enough to be included into 2.5.1? (Dependency updates are usually not something one should do lightly)

Looks like this PR hasn't been updated in a while so we're going to go ahead and mark this as Stale.
Feel free to remove the Stale label if you feel this was a mistake.
If you are unable to remove the Stale label please contact a maintainer in order to do so.
If you want the bot to never mark this PR stale again, add the no-stale label.
Stale pull requests will automatically be closed after 30 days of inactivity.

For the record, this issue has been resolved by #143908