Check the shipped device code covers the GPUs a wheel claims - #21567
Open
shoumikhin wants to merge 11 commits into
Open
Check the shipped device code covers the GPUs a wheel claims#21567shoumikhin wants to merge 11 commits into
shoumikhin wants to merge 11 commits into
Conversation
Contributor
Author
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/21567
Note: Links to docs will display an error until the docs builds have been completed. ❗ 1 Active SEVsThere are 1 currently active SEVs. If your PR is affected, please view them below: ❌ 57 New Failures, 1 Cancelled Job, 23 Pending, 2 Unrelated FailuresAs of commit d2f77f5 with merge base 4b4df96 ( NEW FAILURES - The following jobs have failed:
CANCELLED JOB - The following job was cancelled. Please retry:
FLAKY - The following jobs failed but were likely due to flakiness present on trunk:
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
This was referenced Aug 4, 2026
shoumikhin
added a commit
that referenced
this pull request
Aug 4, 2026
A CUDA wheel can install cleanly, load its libraries, and still fail the moment a
model runs, because GPU device code is compiled per architecture. If a wheel was
built for one GPU generation, it is fine on that generation and broken everywhere
else the release row promised, and the failure looks like a model problem rather
than a packaging one.
Add a check that reads the architectures the build asked for and confirms each one
is present in the shipped accelerator libraries:
✓ device code covers every claimed GPU architecture: [80, 90, 100, 120]
The check skips with a stated reason when a build named no architectures, so the
CPU wheels are unaffected, and when the inspection tool is unavailable.
ghstack-source-id: 2efc906
ghstack-comment-id: 5174656934
Pull-Request: #21567
shoumikhin
changed the base branch from
gh/shoumikhin/84/head
to
gh/shoumikhin/86/head
August 4, 2026 05:23
shoumikhin
added a commit
that referenced
this pull request
Aug 4, 2026
A CUDA wheel can install cleanly, load its libraries, and still fail the moment a
model runs, because GPU device code is compiled per architecture. If a wheel was
built for one GPU generation, it is fine on that generation and broken everywhere
else the release row promised, and the failure looks like a model problem rather
than a packaging one.
Add a check that reads the architectures the build asked for and confirms each one
is present in the shipped accelerator libraries:
✓ device code covers every claimed GPU architecture: [80, 90, 100, 120]
The check skips with a stated reason when a build named no architectures, so the
CPU wheels are unaffected, and when the inspection tool is unavailable.
ghstack-source-id: 2efc906
ghstack-comment-id: 5174656934
Pull-Request: #21567
shoumikhin
added a commit
that referenced
this pull request
Aug 4, 2026
A CUDA wheel can install cleanly, load its libraries, and still fail the moment a
model runs, because GPU device code is compiled per architecture. If a wheel was
built for one GPU generation, it is fine on that generation and broken everywhere
else the release row promised, and the failure looks like a model problem rather
than a packaging one.
Add a check that reads the architectures the build asked for and confirms each one
is present in the shipped accelerator libraries:
✓ device code covers every claimed GPU architecture: [80, 90, 100, 120]
The check skips with a stated reason when a build named no architectures, so the
CPU wheels are unaffected, and when the inspection tool is unavailable.
ghstack-source-id: 2efc906
ghstack-comment-id: 5174656934
Pull-Request: #21567
shoumikhin
changed the base branch from
gh/shoumikhin/86/head
to
gh/shoumikhin/87/head
August 4, 2026 06:35
shoumikhin
added a commit
that referenced
this pull request
Aug 4, 2026
A CUDA wheel can install cleanly, load its libraries, and still fail the moment a
model runs, because GPU device code is compiled per architecture. If a wheel was
built for one GPU generation, it is fine on that generation and broken everywhere
else the release row promised, and the failure looks like a model problem rather
than a packaging one.
Add a check that reads the architectures the build asked for and confirms each one
is present in the shipped accelerator libraries:
✓ device code covers every claimed GPU architecture: [80, 90, 100, 120]
The check skips with a stated reason when a build named no architectures, so the
CPU wheels are unaffected, and when the inspection tool is unavailable.
ghstack-source-id: 04d67a7
ghstack-comment-id: 5174656934
Pull-Request: #21567
shoumikhin
added a commit
that referenced
this pull request
Aug 4, 2026
A CUDA wheel can install cleanly, load its libraries, and still fail the moment a
model runs, because GPU device code is compiled per architecture. If a wheel was
built for one GPU generation, it is fine on that generation and broken everywhere
else the release row promised, and the failure looks like a model problem rather
than a packaging one.
Add a check that reads the architectures the build asked for and confirms each one
is present in the shipped accelerator libraries:
✓ device code covers every claimed GPU architecture: [80, 90, 100, 120]
The check skips with a stated reason when a build named no architectures, so the
CPU wheels are unaffected, and when the inspection tool is unavailable.
ghstack-source-id: 04d67a7
ghstack-comment-id: 5174656934
Pull-Request: #21567
shoumikhin
added a commit
that referenced
this pull request
Aug 4, 2026
A CUDA wheel can install cleanly, load its libraries, and still fail the moment a
model runs, because GPU device code is compiled per architecture. If a wheel was
built for one GPU generation, it is fine on that generation and broken everywhere
else the release row promised, and the failure looks like a model problem rather
than a packaging one.
Add a check that reads the architectures the build asked for and confirms each one
is present in the shipped accelerator libraries:
✓ device code covers every claimed GPU architecture: [80, 90, 100, 120]
The check skips with a stated reason when a build named no architectures, so the
CPU wheels are unaffected, and when the inspection tool is unavailable.
ghstack-source-id: dffdcff
ghstack-comment-id: 5174656934
Pull-Request: #21567
shoumikhin
added a commit
that referenced
this pull request
Aug 4, 2026
A CUDA wheel can install cleanly, load its libraries, and still fail the moment a
model runs, because GPU device code is compiled per architecture. If a wheel was
built for one GPU generation, it is fine on that generation and broken everywhere
else the release row promised, and the failure looks like a model problem rather
than a packaging one.
Add a check that reads the architectures the build asked for and confirms each one
is present in the shipped accelerator libraries:
✓ device code covers every claimed GPU architecture: [80, 90, 100, 120]
The check skips with a stated reason when a build named no architectures, so the
CPU wheels are unaffected, and when the inspection tool is unavailable.
ghstack-source-id: dffdcff
ghstack-comment-id: 5174656934
Pull-Request: #21567
shoumikhin
added a commit
that referenced
this pull request
Aug 4, 2026
A CUDA wheel can install cleanly, load its libraries, and still fail the moment a
model runs, because GPU device code is compiled per architecture. If a wheel was
built for one GPU generation, it is fine on that generation and broken everywhere
else the release row promised, and the failure looks like a model problem rather
than a packaging one.
Add a check that reads the architectures the build asked for and confirms each one
is present in the shipped accelerator libraries:
✓ device code covers every claimed GPU architecture: [80, 90, 100, 120]
The check skips with a stated reason when a build named no architectures, so the
CPU wheels are unaffected, and when the inspection tool is unavailable.
ghstack-source-id: 3103a04
ghstack-comment-id: 5174656934
Pull-Request: #21567
shoumikhin
added a commit
that referenced
this pull request
Aug 4, 2026
A CUDA wheel can install cleanly, load its libraries, and still fail the moment a
model runs, because GPU device code is compiled per architecture. If a wheel was
built for one GPU generation, it is fine on that generation and broken everywhere
else the release row promised, and the failure looks like a model problem rather
than a packaging one.
Add a check that reads the architectures the build asked for and confirms each one
is present in the shipped accelerator libraries:
✓ device code covers every claimed GPU architecture: [80, 90, 100, 120]
The check skips with a stated reason when a build named no architectures, so the
CPU wheels are unaffected, and when the inspection tool is unavailable.
ghstack-source-id: b2f2a6b
ghstack-comment-id: 5174656934
Pull-Request: #21567
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
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.
A CUDA wheel can install cleanly, load its libraries, and still fail the moment a
model runs, because GPU device code is compiled per architecture. If a wheel was
built for one GPU generation, it is fine on that generation and broken everywhere
else the release row promised, and the failure looks like a model problem rather
than a packaging one.
Add a check that reads the architectures the build asked for and confirms each one
is present in the shipped accelerator libraries:
The check skips with a stated reason when a build named no architectures, so the
CPU wheels are unaffected, and when the inspection tool is unavailable.