Skip to content

[Release 0.6] update torchao pin #9947

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

Merged
merged 4 commits into from
Apr 8, 2025
Merged

[Release 0.6] update torchao pin #9947

merged 4 commits into from
Apr 8, 2025

Conversation

metascroy
Copy link
Contributor

@metascroy metascroy commented Apr 7, 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 metascroy requested a review from GregoryComer as a code owner April 7, 2025 22:12
Copy link

pytorch-bot bot commented Apr 7, 2025

🔗 Helpful Links

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

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

✅ No Failures

As of commit 9c9bf25 with merge base 52b4483 (image):
💚 Looks good so far! There are no failures yet. 💚

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

@facebook-github-bot facebook-github-bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label Apr 7, 2025
@metascroy metascroy requested review from mergennachin and jathu April 7, 2025 22:14
@metascroy metascroy added module: build/install Issues related to the cmake and buck2 builds, and to installing ExecuTorch topic: not user facing labels Apr 7, 2025
@@ -61,7 +61,7 @@ jobs:
post-script: ${{ matrix.post-script }}
package-name: ${{ matrix.package-name }}
# Meta's macOS runners do not have Xcode, so use GitHub's runners.
runner-type: macos-latest-xlarge
runner-type: macos-15-xlarge
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

torchao does not build on < macos15 due to "std::aligned_alloc" not being implemented until macos15.

atalman pushed a commit to pytorch/test-infra that referenced this pull request Apr 8, 2025
We are trying to bump the torchao pin in ExecuTorch, but CI jobs fail:
pytorch/executorch#9947.

In particular this job fails:
https://github.com/pytorch/executorch/actions/runs/14321828652/job/40140080161?pr=9947

The root cause is
"/Users/runner/work/executorch/executorch/pytorch/executorch/third-party/ao/torchao/experimental/../../torchao/experimental/ops/memory.h:22:34:
error: 'aligned_alloc' is only available on macOS 10.15 or newer
[-Werror,-Wunguarded-availability-new]"

This is because the test infra defines the "export
MACOSX_DEPLOYMENT_TARGET=10.13".
Copy link
Contributor

@mergennachin mergennachin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Okay great, let's cherry-pick onto ET 0.6 branch.

pyproject.toml Outdated
@@ -66,6 +66,8 @@ dependencies=[
"ruamel.yaml",
"sympy",
"tabulate",
# Keep this version in sync with: third-party/ao pin
"torchao==0.10.0",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In main, how would you depend on latest ao changes? I'm worried that if you bump the hash in third-party/ao (that may not have the a dedicated release) and it becomes inconsistent and confusing.

Here's what I suggest

In main:

  • Only update third-party/ao to a hash that is consistent with 0.10.0. But not update pyproject.toml

This is not 100% necessary but it's good because (1) we're testing the CI in main (2) making sure main's hash is not older than release branch's

In release branch branch:

  • update third-party/ao to a hash that is consistent with 0.10.0.
  • update pyproject.toml to be 0.10.0
  • update the release checklist to reflect this new process about pinning to torchao.

@mergennachin
Copy link
Contributor

Also in the summary of the PR, please add context and corresponding issue (#9940)

@metascroy metascroy changed the title Update torchao pin [Release 0.6] update torchao pin Apr 8, 2025
@metascroy metascroy merged commit f9c3f63 into main Apr 8, 2025
167 checks passed
@metascroy metascroy deleted the up-torchao branch April 8, 2025 19:04
kirklandsign pushed a commit that referenced this pull request 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.
keyprocedure pushed a commit to keyprocedure/executorch that referenced this pull request 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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ciflow/trunk CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. module: build/install Issues related to the cmake and buck2 builds, and to installing ExecuTorch topic: not user facing
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants