Include cublas error details when getting cublas handle fails #3695
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.
I've been getting hard-to-debug errors in some DeepSpeed runs. During initialization, one of the worker processes raises
RuntimeError: Fail to create cublas handle.
with no further details, which feels pretty mysterious.This change includes details of the failure status by using https://docs.nvidia.com/cuda/cublas/#cublasgetstatusname and https://docs.nvidia.com/cuda/cublas/#cublasgetstatusstring
original error message (using deepspeed 0.9.2):

RuntimeError: Fail to create cublas handle.
new error message with this change:

RuntimeError: Failed to create cublas handle: CUBLAS_STATUS_NOT_INITIALIZED the library was not initialized
This is still not a great error message, but it has better search results (most results suggest that it's due to running out of GPU memory; bizarrely some people also report removing
~/.nv
fixes it...).