Skip to content

Conversation

@malfet
Copy link
Contributor

@malfet malfet commented Dec 27, 2024

And remove python>=3.9 check as it currently covers all supported python versions

Fixes #143907

And remove python>=3.9 check as it currently covers all supported python versions
@pytorch-bot
Copy link

pytorch-bot bot commented Dec 27, 2024

🔗 Helpful Links

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

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

⏳ No Failures, 2 Pending

As of commit ffb5012 with merge base a20765a (image):
💚 Looks good so far! There are no failures yet. 💚

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

@pytorch-bot pytorch-bot bot added the topic: not user facing topic category label Dec 27, 2024
@malfet malfet requested a review from a team December 27, 2024 14:56
@Skylion007
Copy link
Collaborator

Also probably a good backport candidate for 2.6

@malfet
Copy link
Contributor Author

malfet commented Dec 27, 2024

Also probably a good backport candidate for 2.6

Hmm, let me check meta information, I thought that requirements.txt are just for local development, while PyPI wheels has an unpinned dependency.

@malfet
Copy link
Contributor Author

malfet commented Dec 27, 2024

@pytorchbot merge

@pytorch-bot pytorch-bot bot added the ciflow/trunk Trigger trunk jobs on your pull request label Dec 27, 2024
@pytorchmergebot
Copy link
Collaborator

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

@malfet
Copy link
Contributor Author

malfet commented Dec 27, 2024

@pytorchbot merge -f "I trust ROCM builds will work"

@pytorchmergebot
Copy link
Collaborator

The merge job was canceled or timed out. This most often happen if two merge requests were issued for the same PR, or if merge job was waiting for more than 6 hours for tests to finish. In later case, please do not hesitate to reissue the merge command
For more information see pytorch-bot wiki.

@pytorchmergebot
Copy link
Collaborator

Merge started

Your change will be merged immediately since you used the force (-f) flag, bypassing any CI checks (ETA: 1-5 minutes). Please use -f as last resort and instead consider -i/--ignore-current to continue the merge ignoring current failures. This will allow currently pending tests to finish and report signal before the merge.

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

@evan0greenup
Copy link

@malfet , is it possible to add wildcard in sympy version like 1.13.* or >=1.13, because in the future when sympy release new version, this issue will arise again. And it is rare for sympy to have break change.

galexite pushed a commit to graphcore/pytorch-fork that referenced this pull request Dec 30, 2024
@github-actions github-actions bot deleted the malfet-patch-14 branch January 28, 2025 02:04
fffrog added a commit that referenced this pull request Feb 14, 2025
As the title stated.

**Previous PR:**
#143908

**ISSUE Related:**
#147144

ghstack-source-id: b1918e6
Pull Request resolved: #147197
pytorchmergebot pushed a commit that referenced this pull request Feb 16, 2025
As the title stated.

**Previous PR:**
#143908

**ISSUE Related:**
#147144

ghstack-source-id: cf58b37
Pull Request resolved: #147197
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ciflow/inductor ciflow/trunk Trigger trunk jobs on your pull request Merged topic: not user facing topic category

Projects

None yet

Development

Successfully merging this pull request may close these issues.

update sympy version in requirement.txt

6 participants