-
Notifications
You must be signed in to change notification settings - Fork 537
torchao not installed by default for ExecuTorch 0.6 RC #9940
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
Milestone
Comments
metascroy
added a commit
that referenced
this issue
Apr 8, 2025
This PR is the first step to addressing #9940 and making torchao installable on ET/release/0.6. 1. This PR bumps torchao pin to torchao/release/0.10.0 branch. 2. We will follow-up with a PR in release/0.6 to bump the pin and add torchao==0.10.0 to the pyproject.toml file.
metascroy
added a commit
that referenced
this issue
Apr 8, 2025
This PR bumps the torchao pins for the ExecuTorch 0.6 release branch to the torchao 0.10.0 release: 1. The pin in third-party/ao is bumped to branch "release/0.10.0". 2. We add "torchao==0.10.0" to the pyproject.toml. This is intended to address #9940 and follows the corresponding bin bump in third-party/ao on main (https://github.com/pytorch/executorch/pull/9947/files).
kirklandsign
pushed a commit
that referenced
this issue
Apr 11, 2025
This PR is the first step to addressing #9940 and making torchao installable on ET/release/0.6. 1. This PR bumps torchao pin to torchao/release/0.10.0 branch. 2. We will follow-up with a PR in release/0.6 to bump the pin and add torchao==0.10.0 to the pyproject.toml file.
This was referenced Apr 14, 2025
keyprocedure
pushed a commit
to keyprocedure/executorch
that referenced
this issue
Apr 21, 2025
This PR is the first step to addressing pytorch#9940 and making torchao installable on ET/release/0.6. 1. This PR bumps torchao pin to torchao/release/0.10.0 branch. 2. We will follow-up with a PR in release/0.6 to bump the pin and add torchao==0.10.0 to the pyproject.toml file.
This was referenced Apr 28, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
🐛 Describe the bug
After I install
The following commmand doesn't work:
Let's either
If we go with the first route, one thing to make sure is that third-party/ao submodule hash is the same as pinned torchao release
Versions
The text was updated successfully, but these errors were encountered: