-
Notifications
You must be signed in to change notification settings - Fork 646
Bump the PyTorch pin to 20250811 #13334
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
Stack from ghstack (oldest at bottom): |
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/13334
Note: Links to docs will display an error until the docs builds have been completed. ❌ 4 New Failures, 4 Cancelled JobsAs of commit 8c7ef6e with merge base 8e73c09 ( NEW FAILURES - The following jobs have failed:
CANCELLED JOBS - The following jobs were cancelled. Please retry:
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
[ghstack-poisoned]
failing zephyr jobs seem to be using the old version of bit_cast.h somehow. inclined to ignore those and hope they clear on land, but I'll see if I can find anyone else who has seen this behavior first. unittest-arm-backend-with-no-fvp (test_pytest_ops) / linux-job (pull_request) failure looks like a flake, rerunning. |
happy to ignore test-llava-runner-linux failure; it's known to segfault sometimes |
it looks like zephyr is somehow pinned to an old executorch version. going to talk to @BujSet soon |
@BujSet says we can have zephyr tests point at the current ExecuTorch source and he'll try to get around to that soon. |
No description provided.