-
Notifications
You must be signed in to change notification settings - Fork 418
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Manual cherry-pick to update numpy as well as all dependencies #7727
Conversation
mergennachin
commented
Jan 17, 2025
•
edited
Loading
edited
- Install torchao by default (Install torchao by default #7470)
- Upgrade numpy version requirement to 2.0 (Upgrade numpy version requirement to 2.0 #7599)
- Update torchtune pin to release version
- [Arm] TOSA reference model update
Upgrade numpy version requirement to Summary: 1.21 is too old now. For 3.10 or above, we should be able to use 2.0.0 We are already on CoreMLTools 8.1, which is https://github.com/apple/coremltools/blob/8.1/reqs/build.pip We had to upgrade to the latest transformers as well (cherry picked from commit a7b5297)
(cherry picked from commit a18f6e8)
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/7727
Note: Links to docs will display an error until the docs builds have been completed. ❌ 3 New Failures, 16 PendingAs of commit eb4529a with merge base 9069017 (): NEW FAILURES - The following jobs have failed:
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
I just realized that we have to update the torchtune pin to release version, just like how we do for everything else (torch, torchaudio, torchvision etc) Otherwise, even if we update the nightly pin, when someone uses the release binary in a few months, one of its dependencies, torchtune, will not be working Initially I tried to cherry-pick (#7670), but later manually override with release version. |
Ah, got it. It seems that your diff seems to accomplish that; would I be correct to assume that the only next steps would be to update the release workflow to say that torchtune must be updated as well? |
Yes, that would be correct |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@mergennachin yup should be fine as long as tests past