-
Notifications
You must be signed in to change notification settings - Fork 25.5k
Add binary size check to validate current limits for binaries released to pypi #159768
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
base: main
Are you sure you want to change the base?
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/159768
Note: Links to docs will display an error until the docs builds have been completed. ❗ 1 Active SEVsThere are 1 currently active SEVs. If your PR is affected, please view them below: ✅ You can merge normally! (1 Unrelated Failure)As of commit a29e7df with merge base e5a81aa ( UNSTABLE - The following job is marked as unstable, possibly due to flakiness on trunk:
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
|
||
CUDA_AARCH64_ARCHES = ["12.9-aarch64"] | ||
|
||
# current binary limits for each platform released to PyPI |
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.
Here are both CU 12.8 and CU 12.9 are listed since we will probably promote Experimental CUDA 12.9 builds to pypi in future releases
Looks like this PR hasn't been updated in a while so we're going to go ahead and mark this as |
Adding check in linux binary validations, trying to mitigate binary size increase for binaries released to pypi:
Reference issues:
2.7.0: #150647
2.8.0: #159515
Trying to mitigate:
#159516