Skip to content

Refresh the release runner groups on release tags - #9669

Open
huydhn wants to merge 3 commits into
mainfrom
osdc/release-runner-groups-refresh
Open

huydhn wants to merge 3 commits into
mainfrom
osdc/release-runner-groups-refresh

Conversation

@huydhn

@huydhn huydhn commented Sep 12, 2026

Copy link
Copy Markdown
Contributor

Last of three taking vision's Linux CI off EC2: #9667 moves the CI jobs, #9668 the wheel builds, this keeps the runner groups in sync.

Mirrors the workflow of the same name in pytorch/pytorch and pytorch/executorch. On a release or release-candidate tag it reconciles the org-level release runner groups so the workflows this repo builds from stay allow-listed; on a PR touching this file, and on dispatch without the flag, it only prints the diff.

Passes --repo so the run touches only this repository's entries — the groups are shared, and before pytorch/test-infra#8788 the script PATCHed the allow-list to exactly one repo's desired set. That landed, so this now runs against test-infra@main.

Verified against this repo:

Test-channel version anchor: release/0.29
Target refs: main, nightly, release/0.29, release/0.28,
             v0.29.0, v0.29.0-rc2, v0.28.0, v0.28.0-rc5

0 workflows discovered so far, which is correct — nothing here uses a release runner label until #9668 lands, and the script refuses to apply an empty allow-list.

Authored with Claude Code.

@pytorch-bot

pytorch-bot Bot commented Sep 12, 2026

Copy link
Copy Markdown

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/vision/9669

Note: Links to docs will display an error until the docs builds have been completed.

❗ 1 Active SEVs

There are 1 currently active SEVs. If your PR is affected, please view them below:

❌ 1 Unclassified Failure

As of commit 5dd40fb with merge base bb9733d (image):

UNCLASSIFIED FAILURE - DrCI could not classify the following job because the workflow did not run on the merge base. The failure may be pre-existing on trunk or introduced by this PR:

This comment was automatically generated by Dr. CI and updates every 15 minutes.

@meta-cla meta-cla Bot added the cla signed label Sep 12, 2026
@huydhn
huydhn requested a review from atalman September 12, 2026 23:05
@huydhn
huydhn marked this pull request as ready for review September 12, 2026 23:06
Mirrors the workflow of the same name in pytorch/pytorch and
pytorch/executorch. On a release or release-candidate tag it reconciles the
org-level release runner groups so the workflows this repository builds from
stay allow-listed; on a pull request touching this file, and on dispatch without
the flag, it only prints the diff.

Passes --repo so the run touches only this repository's entries. The groups are
shared, and before pytorch/test-infra#8788 the script PATCHed the allow-list to
exactly one repository's desired set, which would have had each consumer remove
the others' entries on every release. That PR also replaces the
/branches?protected=true scan the anchor used to need, which times out on large
repositories.

Reads RUNNER_GROUP_TOKEN from the runner-group environment, as pytorch/pytorch
and pytorch/executorch do. A pull request run does not select that environment,
so it falls back to GITHUB_TOKEN and the script takes its discovery-only path.

Authored with Claude Code.
@huydhn
huydhn force-pushed the osdc/release-runner-groups-refresh branch 2 times, most recently from 7313341 to d5d3535 Compare September 12, 2026 23:15
@@ -0,0 +1,55 @@
name: Refresh release runner groups

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Top-level description of what this does and why it's needed would be helpful!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants