Skip to content

Conversation

GregoryComer
Copy link
Member

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.

Copy link

pytorch-bot bot commented Sep 17, 2025

🔗 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 Failures

As of commit 4fdb1af with merge base e0dda90 (image):

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.

@meta-cla meta-cla 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 Sep 17, 2025
Copy link

This PR needs a release notes: label

If your change should be included in the release notes (i.e. would users of this library care about this change?), please use a label starting with release notes:. This helps us keep track and include your important work in the next release notes.

To add a label, you can comment to pytorchbot, for example
@pytorchbot label "release notes: none"

For more information, see
https://github.com/pytorch/pytorch/wiki/PyTorch-AutoLabel-Bot#why-categorize-for-release-notes-and-how-does-it-work.

@GregoryComer GregoryComer changed the base branch from main to release/1.0 September 17, 2025 21:56
@GregoryComer GregoryComer marked this pull request as ready for review September 17, 2025 21:56
@GregoryComer GregoryComer changed the title Apply release workflow changes for 1.0 [RELEASE ONLY CHANGES] Apply release workflow changes for 1.0 Sep 17, 2025
@GregoryComer GregoryComer force-pushed the apply-release-changes-1-0 branch from 3a36ff0 to edc45b3 Compare September 17, 2025 22:33
@GregoryComer GregoryComer temporarily deployed to upload-benchmark-results September 17, 2025 23:07 — with GitHub Actions Inactive
@psiddh
Copy link
Contributor

psiddh commented Sep 17, 2025

Couple of CI failures . unrelated ?

@GregoryComer
Copy link
Member Author

Couple of CI failures . unrelated ?

Yeah, looks like an infra failure. I'm retrying to make sure.

@GregoryComer GregoryComer temporarily deployed to upload-benchmark-results September 18, 2025 00:20 — with GitHub Actions Inactive
@GregoryComer
Copy link
Member Author

Rebasing and re-running CI. If everything looks good, I'll merge shortly.

@GregoryComer GregoryComer temporarily deployed to upload-benchmark-results September 18, 2025 22:56 — with GitHub Actions Inactive
@GregoryComer GregoryComer temporarily deployed to upload-benchmark-results September 19, 2025 00:27 — with GitHub Actions Inactive
@GregoryComer GregoryComer temporarily deployed to upload-benchmark-results September 19, 2025 01:22 — with GitHub Actions Inactive
@GregoryComer GregoryComer temporarily deployed to upload-benchmark-results September 19, 2025 07:10 — with GitHub Actions Inactive
@GregoryComer
Copy link
Member Author

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.

@GregoryComer GregoryComer merged commit 2fecf2c into release/1.0 Sep 19, 2025
285 of 302 checks passed
@GregoryComer GregoryComer deleted the apply-release-changes-1-0 branch September 19, 2025 21:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants