Skip to content

ci: fix macOS PyTorch wheel cache key for branch-ref pins#19350

Open
rascani wants to merge 1 commit intopytorch:mainfrom
rascani:fix-macos-torch-cache-key
Open

ci: fix macOS PyTorch wheel cache key for branch-ref pins#19350
rascani wants to merge 1 commit intopytorch:mainfrom
rascani:fix-macos-torch-cache-key

Conversation

@rascani
Copy link
Copy Markdown
Contributor

@rascani rascani commented May 6, 2026

Summary

install_pytorch_and_domains constructs the cached-wheel URL using ${TORCH_VERSION:0:7}, which gives "release" when the pin is a branch ref like release/2.11. The upload code uses the basename of dist/*.whl, which is whatever PyTorch's setup.py wrote — always the resolved commit hash (e.g. +git70d99e9). The two never match, so every macOS run misses the cache and does a ~30-minute source build even though the wheel for the current pin's HEAD is already in S3.

Resolve the hash via git rev-parse --short=7 HEAD after git checkout, so download and upload agree. Commit-hash pins are unchanged (the first 7 chars already equaled the resolved hash).

Authored with Claude Code.

Test plan

CI

`install_pytorch_and_domains` constructs the cached-wheel URL using
`${TORCH_VERSION:0:7}`, which gives "release" when the pin is a
branch ref like `release/2.11`. The upload code uses the basename of
`dist/*.whl`, which is whatever PyTorch's setup.py wrote — always the
resolved commit hash (e.g. `+git70d99e9`). The two never match, so
every macOS run misses the cache and does a ~30-minute source build
even though the wheel for the current pin's HEAD is already in S3.

Resolve the hash via `git rev-parse --short=7 HEAD` after `git
checkout`, so download and upload agree. Commit-hash pins are
unchanged (the first 7 chars already equaled the resolved hash).

Authored with Claude Code.
@pytorch-bot
Copy link
Copy Markdown

pytorch-bot Bot commented May 6, 2026

🔗 Helpful Links

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

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

❌ 4 Cancelled Jobs, 46 Unrelated Failures

As of commit 319b9e6 with merge base 851cffb (image):

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 May 6, 2026
@github-actions
Copy link
Copy Markdown

github-actions Bot commented May 6, 2026

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

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