-
Notifications
You must be signed in to change notification settings - Fork 305
Preserve memory pool CUDA errors and harden OOM tests #2084
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
kkraus14
merged 7 commits into
NVIDIA:main
from
rwgk:nvbugs5815123_fix_masking_oom_as_invalid_value
May 15, 2026
Merged
Changes from 5 commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
4255902
cuda.core: preserve memory pool CUDA errors
rwgk 52879fd
test: skip unsupported managed pool warnings
rwgk 93e86ec
test: xfail default mempool interop OOM
rwgk 52a834f
test: xfail graph mempool allocation OOM
rwgk 883b1a7
Merge branch 'main' into nvbugs5815123_fix_masking_oom_as_invalid_value
rwgk fe741b3
Merge branch 'main' into nvbugs5815123_fix_masking_oom_as_invalid_value
rwgk 1257b43
cuda.core: clarify internal empty-handle fallback errors
rwgk 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.
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.
get_device_mempoolisn't a public API, where if I'm an end user this error message is somewhat confusing and non-actionable. I think the situation we're in here is that if an empty handle is returned but the last CUDA return code wasCUDA_SUCCESS, thenHANDLE_RETURNwouldn't throw and so we need some kind of generic catch?Maybe something like?
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.
Applied consistently: commit 1257b43
Thanks!
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.
I am so very confused... Isn't
HANDLE_RETURNalready raising when an error happens? @Andy-Jost Is it possible that the handle creation/retrieval could fail, butCUDA_SUCCESSis returned?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.
Bugs happen. It would be extremely confusing if an upstream bug isn't caught here. Achieving safety here is super cheap, i.e. the benefit/cost ratio is a no brainer.