fix(Python): Ensure we don't call cuMemAlloc with 0 bytesize#534
Merged
paleolimbot merged 2 commits intoapache:mainfrom Jun 20, 2024
Merged
fix(Python): Ensure we don't call cuMemAlloc with 0 bytesize#534paleolimbot merged 2 commits intoapache:mainfrom
paleolimbot merged 2 commits intoapache:mainfrom
Conversation
Contributor
Author
|
I see that this logic is being overhauled in #509. If the maintainers want to close this PR out, that's fine by me! It's probably worth including the changes to the tests though. |
paleolimbot
approved these changes
Jun 20, 2024
Member
paleolimbot
left a comment
There was a problem hiding this comment.
Thank you!
(Even though we're rewriting this, this is a nice quality-of-life improvement in the tests!)
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.
According to the CUDA docs for cuMemAlloc:
We end up calling
cuMemAlloc()with0bytesize when allocating device buffers with no null mask. Thus, the following change was causingnanoarrow_device_cuda_testto fail:In this PR, I've fixed this by simply skipping the call to
cuMemAlloc. The resulting buffer will havenullptras itsdatamember and0as itssize_bytes, which I believe is the desired outcome.I also modified the test above to include cases with no nulls.