NEW: Make event timing error messages more specific and actionable
Description
closes #556
The CUDA driver provides different error messages for various errors when trying to compute elapsed time, and the documentation explains each of these scenarious. Surface each of these to Python uses with actionable error messages.
Checklist
- [x] New or existing tests cover these changes.
- [ ] The documentation is up to date with these changes.
* Not sure what documentation should be added. Sometimes python functions document what errors are raised, but sub doesn't have a docs section.
This pull request requires additional validation before any workflows can run on NVIDIA's runners.
Pull request vetters can view their responsibilities here.
Contributors can view more details about this message here.
/ok to test 8782dfadb0f1a04f135ca21cab9ae3602ebd59bb
/ok to test 8782dfadb0f1a04f135ca21cab9ae3602ebd59bb
Doc Preview CI :---: |
:rocket: View preview athttps://nvidia.github.io/cuda-python/pr-preview/pr-559/
|
https://nvidia.github.io/cuda-python/pr-preview/pr-559/cuda-core/
|
https://nvidia.github.io/cuda-python/pr-preview/pr-559/cuda-bindings/
|
Preview will be ready when the GitHub Pages deployment is complete.
I think we are set up so that the CI will never trigger automatically. Only of you leave the ok to test comment. Certainly in draft mode.
/ok to test 99218bb9a7d53bbe3ff2d0f0d1cc97e0547bcfd8
/ok to test add0ba1
/ok to test 638990d
/ok to test 9904f3d
Thanks for nice improvements, Daniel!
Doc Preview CI :---: Preview removed because the pull request was closed or merged.