Skip to content

Keep full backend matrices for relevant changes and sample unrelated main pushes - #24722

Draft
JacobSzwejbka wants to merge 1 commit into
pytorch:mainfrom
JacobSzwejbka:ci-cost/9-backend-path-aware
Draft

JacobSzwejbka wants to merge 1 commit into
pytorch:mainfrom
JacobSzwejbka:ci-cost/9-backend-path-aware

Conversation

@JacobSzwejbka

Copy link
Copy Markdown
Contributor

Replacement for #24672.

Keep full QNN, Arm/TOSA/Ethos-U/VGF, XNNPACK and Vulkan matrices on relevant backend changes and shared export, runtime, operator, model, build, installer, dependency-pin and test changes. Only unrelated PRs and unsampled main pushes get the reduced matrices. Main sampling reads the existing CI run decision.

Full scheduled, manual, tag and release-branch coverage is preserved. No release-publication workflows, viable/strict rules, merge requirements or sample-decision implementation are changed.

The selector uses complete Git diffs, including deletions and renames. Missing or unrecognized diff information forces full coverage. Existing callers without a reduced matrix continue to use their full flow list.

Review the policy and tests first, then the shared backend workflow and four caller changes. The policy avoids deferring quantized and target-specific regressions from relevant changes until the nightly.

Validation

Seven policy tests pass, including related/unrelated changes, sampling, existing full-run events, deletion/rename handling, more than 300 changed files, unknown bases and invalid matrices. Actionlint, Black/usort and git diff --check pass locally. GitHub CI is pending.

Authored with AI assistance using Codex.

Keep quantized and target-specific flows on backend, export, runtime, build, dependency and test changes. Reserve reduced matrices for unrelated PRs and unsampled main pushes, using the existing sampling decision. Complete Git diffs include deletions and renames. Release coverage, publication and viable/strict rules are unchanged.

Authored with Codex.
@pytorch-bot

pytorch-bot Bot commented Nov 6, 2026 •

Copy link
Copy Markdown

🔗 Helpful Links

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

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

❌ 20 New Failures, 98 Unrelated Failures, 1 Unclassified Failure

As of commit 552bdb3 with merge base c7157c9 (image):

NEW FAILURES - The following jobs have failed:

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:

FLAKY - The following jobs failed but were likely due to flakiness present on trunk:

BROKEN TRUNK - The following jobs failed but were present on the merge base:

👉 Rebase onto the `viable/strict` branch to avoid these failures

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 Nov 6, 2026
@github-actions

github-actions Bot commented Nov 6, 2026

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.

This branch has not been deployed

No deployments
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.

1 participant