-
Notifications
You must be signed in to change notification settings - Fork 683
[RELEASE ONLY CHANGES] Apply release workflow changes for 1.0 #14390
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
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/14390
Note: Links to docs will display an error until the docs builds have been completed. ❌ 3 New Failures, 2 Cancelled Jobs, 5 Unrelated FailuresAs of commit 4fdb1af with merge base e0dda90 ( NEW FAILURES - The following jobs have failed:
CANCELLED JOBS - The following jobs were cancelled. Please retry:
FLAKY - The following jobs failed but were likely due to flakiness present on trunk:
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
This PR needs a
|
3a36ff0
to
edc45b3
Compare
Couple of CI failures . unrelated ? |
Yeah, looks like an infra failure. I'm retrying to make sure. |
Rebasing and re-running CI. If everything looks good, I'll merge shortly. |
Merging as remaining failures are unrelated. This PR triggers basically every workflow. Backend test jobs will be fixed when cherry-picking the larger runner PR. |
Summary
As described in the release manual, I've run
TEST_INFRA_BRANCH=release/2.9 scripts/release/apply-release-changes.sh
to update workflows to use the release/2.9 test infra branch.