Skip to content

ci: consolidate pinned PyTorch installation - #24605

Open
zingo wants to merge 2 commits into
pytorch:mainfrom
zingo:ci-consolidate-pinned-PyTorch-installation
Open

zingo wants to merge 2 commits into
pytorch:mainfrom
zingo:ci-consolidate-pinned-PyTorch-installation

Conversation

@zingo

@zingo zingo commented Nov 4, 2026 •

Copy link
Copy Markdown
Collaborator

Share the pinned PyTorch installer between Docker and CI setup. Reuse matching builds and preserve the macOS wheel cache. Resolve named refs without cloning and install domain packages even when the pinned torch build is reused.

Verify the exact PyTorch pin and LAPACK support after Linux and macOS dependency installation. Add mocked installer tests.

Authored with Codex.

cc @digantdesai @freddan80 @per @oscarandersson8218 @mansnils @Sebastian-Larsson @robell @rascani

Share the pinned PyTorch installer between Docker and CI setup.
Reuse matching builds and preserve the macOS wheel cache.
Resolve named refs without cloning and install domain packages
even when the pinned torch build is reused.

Verify the exact PyTorch pin and LAPACK support after Linux and
macOS dependency installation. Add mocked installer tests.

Authored with Codex.

Signed-off-by: Zingo Andersen <Zingo.Andersen@arm.com>
Change-Id: Ia35463d87c8757b001c51da72839a3c4e20c77eb
@pytorch-bot

pytorch-bot Bot commented Nov 4, 2026 •

Copy link
Copy Markdown

🔗 Helpful Links

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

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

❌ 24 New Failures, 26 Cancelled Jobs, 2 Pending, 5 Unrelated Failures

As of commit 90eca06 with merge base 5af315a (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:

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 4, 2026
@github-actions github-actions Bot added the ciflow/docker Trigger docker-builds to rebuild and push the CI images for this PR label Nov 4, 2026
@github-actions

github-actions Bot commented Nov 4, 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.

@zingo zingo added help wanted Extra attention is needed ciflow/trunk labels Nov 4, 2026
@zingo zingo added the partner: arm For backend delegation, kernels, demo, etc. from the 3rd-party partner, Arm label Nov 10, 2026

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

ciflow/docker Trigger docker-builds to rebuild and push the CI images for this PR ciflow/trunk CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. help wanted Extra attention is needed partner: arm For backend delegation, kernels, demo, etc. from the 3rd-party partner, Arm

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant