-
Notifications
You must be signed in to change notification settings - Fork 277
cuda.core.system: Better checks for when we expect APIs to be unsupported #1510
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
mdboom
merged 14 commits into
NVIDIA:main
from
mdboom:cuda.core.system-better-compat-check
Jan 22, 2026
Merged
Changes from 1 commit
Commits
Show all changes
14 commits
Select commit
Hold shift + click to select a range
2df0c31
cuda.core.system: Better checks for when we expect APIs to be unsuppo…
mdboom 70a252d
Update cuda_core/tests/system/test_system_device.py
mdboom a9d074b
Update cuda_core/tests/system/conftest.py
mdboom c56e49b
Update cuda_bindings/tests/nvml/conftest.py
mdboom 0808139
Fix importing of conftest.py
mdboom 9b571b4
Fix tests
mdboom 032c4e6
Fix tests
mdboom 9c815cc
Fix a test on T4
mdboom 04cf332
Refactor test helper
mdboom 0545f4b
Use Unicode character
mdboom b97f3c8
Fix imports
mdboom d1b3a52
Add warning if devices are different architectures
mdboom 9064c49
Add some comments
mdboom af03408
Merge remote-tracking branch 'upstream/main' into cuda.core.system-be…
mdboom File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The below came from Cursor (after discarding my
cuda.bindings.tests.helpersidea I posted offline).The idea is that you can give this to Cursor on your end to play with the options.
Suggestion: Deduplicating
unsupported_beforeI noticed we now have two nearly identical
unsupported_beforecontext managers:cuda_bindings/tests/nvml/conftest.pycuda_core/tests/system/conftest.pyThe logic is the same, but they use different API surfaces:
nvml.device_get_architecture(device)device.archnvml.device_get_name(device)device.namenvml.DeviceArchsystem.DeviceArchnvml.NotSupportedErrorsystem.NotSupportedErrorOptions to consider
Option 1: Factory pattern in
cuda_python_test_helpers(recommended)Keep
cuda_python_test_helpersCUDA-agnostic but share the logic via dependency injection:Then in each conftest:
Pros: Single source of truth for the logic,
cuda_python_test_helpersstays CUDA-agnostic.Cons: Slightly more indirection.
Option 2: Let
cuda_python_test_helpersdepend oncuda-bindingsProvide a single nvml-based implementation. cuda.core tests would extract device handles.
Pros: Simpler API.
Cons: Reverses the direction of commit 6afdd5c; ties test helpers to CUDA packages.
Option 3: Accept the duplication
~40 lines duplicated in 2 files. The implementations use different abstraction layers, so some might argue they're legitimately different.
Pros: No new abstractions.
Cons: Bug fixes / enhancements need to be applied twice.
I'd lean toward Option 1 since it keeps the CUDA-agnostic design while eliminating the duplication. Happy to pair on this if you want to explore it further.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As is often the case with these AI tools, Cursor's suggestion is way more complex than it needs to be.
I think we can:
Create a cuda.bindings._test_helpers package to put these sort of "shared" things into. We don't need to include the entire test suite in the
cuda.bindingspackage in order to do this. (This probably requires a little extra design approval before we commit to it).The
cuda.core.systemversion of this helper can just delegate to thecuda.bindings.nvmlone by passing along the handle.