-
Notifications
You must be signed in to change notification settings - Fork 536
Bump PyTorch pin to 2025-03-25 #9578
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
Stack from ghstack (oldest at bottom): |
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/9578
Note: Links to docs will display an error until the docs builds have been completed. ⏳ 1 Pending, 1 Unrelated FailureAs of commit e221434 with merge base c70c208 ( 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. |
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.
Can we do this after our branch cut on Wednesday 6pm?
The reason is that 3-12 is the RC candidate for PT2.7 - anything after that is in the PT2.8
Otherwise, we would have to go back and forth, instead of monotonically increasing the nightly.
Unfortunately, this is the downside of delaying the branch cut and diverging from pytorch timeline |
@mergennachin the branch is cut now, right? |
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.
Thank you for your patience, we can move forward now that its post branch cut
cc @metascroy |
looks like unittest-arm failure are new, CC @digantdesai |
resnapshotted the ARM test. we'll see if it builds. |
pinged @digantdesai for advice on how to proceed with ARM failures |
We have looked into this and have some fixes in the Arm delegate in the works to handle this, hopefully it will be ready tomorrow. |
Fix that hopefully handled the Arm backend problems merged to main e.g. #9834 |
@zingo still one failure on unittest-arm:
|
Sorry we missed that, for some reason that one didn't give us problem in the internal testing. There is a new fix cooking that hopefully be uploaded tomorrow. |
Just merged #9898 |
test-qnn-model is failing on main, test-llava-runner-linux failure looks like a flake, retrying |
Found release from https://hud2.pytorch.org/hud/pytorch/pytorch/nightly/0 .