Skip to content

Include cause exception details in RuntimeError#1

Open
GlenWalker wants to merge 2 commits intomasterfrom
ErrorDescripton
Open

Include cause exception details in RuntimeError#1
GlenWalker wants to merge 2 commits intomasterfrom
ErrorDescripton

Conversation

@GlenWalker
Copy link
Owner

If there is any kind of error when importing monotonic a generic RuntimeError is raised, with the description 'no suitable implementation for this system'. We very occasionally see this on a system where monotonic otherwise works correctly. I suspect ctypes.util.find_library is occasionally failing (as it executes ldconfig under the hood), but it is difficult to tell because details of the cause are lost, and replaced with the generic error message. Include details of the cause exception in the RuntimeError description so this information is not lost.

GlenWalker and others added 2 commits June 7, 2017 13:56
If there is any kind of error when importing monotonic a generic RuntimeError is raised, with the description 'no suitable implementation for this system'. We very occasionally see this on a system where monotonic otherwise works correctly. I suspect ctypes.util.find_library is occasionally failing (as it executes ldconfig under the hood), but it is difficult to tell because details of the cause are lost, and replaced with the generic error message. Include details of the cause exception in the RuntimeError description so this information is not lost.
Trimmed extra space from exception message
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants