Build the Linux wheels on OSDC runners - #9668
Open
huydhn wants to merge 4 commits into
Open
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/vision/9668
Note: Links to docs will display an error until the docs builds have been completed. ❌ 3 Pending, 1 Unclassified FailureAs of commit 9b506c5 with merge base 447c937 ( 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. |
huydhn
marked this pull request as draft
September 12, 2026 22:48
huydhn
force-pushed
the
osdc/wheels-on-osdc
branch
from
September 12, 2026 22:50
da4e59a to
f35477c
Compare
One input on the matrix generator. pytorch/test-infra#8789 adds runner-fleet, which maps each row's validation_runner to its ARC equivalent: release-isolated on the refs these workflows publish from (nightly, main, release/* and the v* candidate tags), regular otherwise, so pull request builds move off EC2 too. x86_64 cpu/rocm/xpu mt-l-x86iavx512-8-64 mt-rel-l-x86iavx512-44-340 x86_64 cuda mt-l-x86aavx2-29-113-a10g mt-rel-l-x86aavx2-29-113-l4 aarch64 any mt-l-arm64g4-16-62 mt-rel-l-arm64g3-44-340 The split matters for x86: the matrix mixes four CPU rows (cpu, rocm10_0, rocm7_14, xpu) with three cuda ones, and test/smoke_test.py guards its CUDA checks with torch.cuda.is_available(), so a cuda row on a CPU runner would skip them rather than fail. aarch64 gets one label either way, matching the runner it replaces: linux.arm64.m7g.4xlarge has no device either. The rocm rows build ROCm wheels on an ordinary CPU builder and need no AMD hardware. Depends on pytorch/test-infra#8789, which also carries the two fixes build_wheels_linux.yml needs to run on an OSDC pod at all. Authored with Claude Code.
huydhn
force-pushed
the
osdc/wheels-on-osdc
branch
from
September 12, 2026 22:57
f35477c to
2948f6c
Compare
Drop before merging. Points both the matrix generator and the wheel build at that PR's branch, and the test-infra checkout with them, so CI here exercises runner-fleet and the two OSDC fixes it carries. Against test-infra main the runner-fleet input does not exist and the call is rejected outright.
huydhn
marked this pull request as ready for review
September 12, 2026 23:01
NicolasHug
reviewed
Sep 14, 2026
| jobs: | ||
| generate-matrix: | ||
| uses: pytorch/test-infra/.github/workflows/generate_binary_build_matrix.yml@main | ||
| uses: pytorch/test-infra/.github/workflows/generate_binary_build_matrix.yml@build-wheels-linux-osdc-workspace |
Member
There was a problem hiding this comment.
Thanks for the PR @huydhn
Can you share more on how these refs should be updated upon releases? I was usually changing main into e.g. release/2.14 both here and below for test-infra-ref.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Second of three taking vision's Linux CI off EC2, after #9667.
One input on the matrix generator. pytorch/test-infra#8789 adds
runner-fleet, which maps each row'svalidation_runnerto its ARC equivalent — release-isolated on the refs these workflows publish from, regular otherwise, so PR builds move off EC2 too.mt-l-x86iavx512-8-64mt-rel-l-x86iavx512-44-340mt-l-x86aavx2-29-113-a10gmt-rel-l-x86aavx2-29-113-l4mt-l-arm64g4-16-62mt-rel-l-arm64g3-44-340The per-row split matters for x86: the matrix mixes four CPU rows with three cuda ones, and
test/smoke_test.pyguards its CUDA checks withtorch.cuda.is_available(), so a cuda row on a CPU runner would skip them rather than fail. aarch64 gets one label either way, matching the runner it replaces —linux.arm64.m7g.4xlargehas no device either.Depends on pytorch/test-infra#8789.
Authored with Claude Code.