Report NVRTC builtin operation failures to the user#196
Merged
kkraus14 merged 1 commit intoNVIDIA:mainfrom Apr 11, 2025
Merged
Conversation
Contributor
Author
|
cc @jiel-nv - this should make it clear if you encounter this issue in future. |
If NVRTC could not load its builtins library, then the user would get an error message like: ``` numba.cuda.cudadrv.error.NvrtcError: Failed to call nvrtcCompileProgram: NVRTC_ERROR_BUILTIN_OPERATION_FAILURE ``` With this change, we specifically transform this error value into a corresponding exception, and provide the user with the log from NVRTC so they can more easily diagnose the issue. They will now see an error like: ``` numba.cuda.cudadrv.error.NvrtcError: NVRTC Compilation failure whilst compiling memsys.cu: nvrtc: error: failed to open libnvrtc-builtins.so.12.8. Make sure that libnvrtc-builtins.so.12.8 is installed correctly. ``` which clearly explains the issue.
gmarkall
force-pushed
the
nvrtc-builtins-failure
branch
from
22db01c to
07d16c4
Compare
kkraus14
approved these changes
Apr 11, 2025
Contributor
kkraus14
left a comment
kkraus14
left a comment
There was a problem hiding this comment.
Would there be any easy way to test this?
Contributor
Author
|
I can't think of an easy way to test this. I tested it manually by renaming the |
gmarkall
added a commit
to gmarkall/numba-cuda
that referenced
this pull request
Apr 22, 2025
- Locate nvvm, libdevice, nvrtc, and cudart from nvidia-*-cu12 wheels (NVIDIA#155) - reinstate test (NVIDIA#226) - Restore PR NVIDIA#185 (Stop Certain Driver API Discovery for "v2") (NVIDIA#223) - Report NVRTC builtin operation failures to the user (NVIDIA#196) - Add Module Setup and Teardown Callback to Linkable Code Interface (NVIDIA#145) - Test CUDA 12.8. (NVIDIA#187) - Ensure RTC Bindings Clamp to the Maximum Supported CC (NVIDIA#189) - Migrate code style to ruff (NVIDIA#170) - Use less GPU memory in test_managed_alloc_driver_undersubscribe. (NVIDIA#188) - Update workflows to always use proxy cache. (NVIDIA#191)
Merged
gmarkall
added a commit
that referenced
this pull request
Apr 22, 2025
- Locate nvvm, libdevice, nvrtc, and cudart from nvidia-*-cu12 wheels (#155) - reinstate test (#226) - Restore PR #185 (Stop Certain Driver API Discovery for "v2") (#223) - Report NVRTC builtin operation failures to the user (#196) - Add Module Setup and Teardown Callback to Linkable Code Interface (#145) - Test CUDA 12.8. (#187) - Ensure RTC Bindings Clamp to the Maximum Supported CC (#189) - Migrate code style to ruff (#170) - Use less GPU memory in test_managed_alloc_driver_undersubscribe. (#188) - Update workflows to always use proxy cache. (#191)
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.
If NVRTC could not load its builtins library, then the user would get an error message like:
With this change, we specifically transform this error value into a corresponding exception, and provide the user with the log from NVRTC so they can more easily diagnose the issue.
They will now see an error like:
which clearly explains the issue.