Skip to content

Move the shared reusable workflows to linux_job_v3 - #22246

Draft
huydhn wants to merge 2 commits into
mainfrom
osdc/v3-reusable
Draft

Move the shared reusable workflows to linux_job_v3#22246
huydhn wants to merge 2 commits into
mainfrom
osdc/v3-reusable

Conversation

@huydhn

@huydhn huydhn commented Aug 28, 2026

Copy link
Copy Markdown
Contributor

Second of six splitting up #22107. Stacked on #22245.

_test_backend, _llm_server, _test_arduino_library, _test_cortex_m_e2e, _test_cortex_m_ops, _test_cadence and _test_riscv. Their docker-image inputs keep taking ci-image:<name>, so callers pass the same values as before.

v3 assumes role/arc through OIDC, and a reusable workflow only gets the permissions each caller hands down, so the nine test-backend-* callers of _test_backend.yml grant id-token: write.

Authored with Claude Code.

@pytorch-bot

pytorch-bot Bot commented Aug 28, 2026

Copy link
Copy Markdown

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/22246

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

❌ 1 New Failure, 1 Cancelled Job, 1 Unrelated Failure

As of commit 878e10a with merge base f665a3b (image):

NEW FAILURE - The following job has failed:

CANCELLED JOB - The following job was cancelled. Please retry:

FLAKY - The following job failed but was 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 Aug 28, 2026
huydhn added a commit that referenced this pull request Aug 28, 2026
Consumer-side counterpart of the docker-builds move, landing here so the
linux_job_v3 migration can build on it.

linux_job_v3 passes docker-image straight to the runner pod's container, which
is pulled before any step runs, so v2's in-job calculate-docker-image -- which
both resolved ci-image:<name> to an ECR reference and waited for docker-builds
to push it -- has nowhere left to run. This emits the same tag docker-builds
computes, and on a commit that touches .ci/docker it waits for that run,
failing fast when the ciflow/docker label means none exists.

Nothing calls it yet; the callers arrive in #22246 onward.

Authored with Claude Code.
@huydhn
huydhn force-pushed the osdc/v3-reusable branch 2 times, most recently from 920dfbe to bd18ec6 Compare August 28, 2026 02:38
_test_backend, _llm_server, _test_arduino_library, _test_cortex_m_e2e,
_test_cortex_m_ops, _test_cadence and _test_riscv. Their docker-image inputs
keep taking ci-image:<name>, so callers pass the same values as before.

v3 assumes role/arc through OIDC, and a reusable workflow only gets the
permissions its caller hands down, so the test-backend-* callers of
_test_backend.yml grant id-token: write.

Authored with Claude Code.
@github-actions

Copy link
Copy Markdown

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.

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

Labels

ci-refresh-hf-cache 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.

1 participant