-
Notifications
You must be signed in to change notification settings - Fork 751
Use torch 2.9 release packages #15168
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
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/15168
Note: Links to docs will display an error until the docs builds have been completed. ❌ 2 Cancelled Jobs, 3 PendingAs of commit d3d8632 with merge base e0dda90 ( CANCELLED JOBS - The following jobs were cancelled. Please retry:
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
|
Do you still need these lines? https://github.com/pytorch/executorch/blob/release/1.0/install_requirements.py#L150-L167 This will be invoked for people install from source in release branch. We should just rely on requirements-examples.txt |
|
CI errors are apparently due to installing the CUDA version of torch. Looking into this now. Edit: Added index-url back into the install_pytorch.sh script to use cpu variants. Re-testing. |
f69c6cf to
d3d8632
Compare
Done. Good catch. |
Summary
Use release 2.9 packages for pytorch and domain libraries in preparation for the final 1.0 release. I'm following the pattern from #13248.