-
Notifications
You must be signed in to change notification settings - Fork 915
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enable Zstandard decompression only when all nvcomp integrations are enabled #10944
Enable Zstandard decompression only when all nvcomp integrations are enabled #10944
Conversation
Codecov Report
@@ Coverage Diff @@
## branch-22.06 #10944 +/- ##
================================================
+ Coverage 86.30% 86.32% +0.02%
================================================
Files 144 144
Lines 22665 22668 +3
================================================
+ Hits 19560 19569 +9
+ Misses 3105 3099 -6
Continue to review full report at Codecov.
|
Despite caveats, this (and the prior PR) should close #9055 right? |
I think it should. Thanks for the reminder. |
I tested this with our spark-rapids integration test (after building with nvcomp-2.3).
When I set it to
|
1 similar comment
I tested this with our spark-rapids integration test (after building with nvcomp-2.3).
When I set it to
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1 lgtm. I tested with this change locally as well.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The CUDF_FAIL macro provides helpful context, like line numbers where the error is thrown, which are lost when the macro is replaced by fail_unsupported
. I would continue using CUDF_FAIL in all cases even though the message is repeated.
cudf/cpp/include/cudf/utilities/error.hpp
Line 110 in 379cc9f
throw cudf::logic_error("cuDF failure at: " __FILE__ ":" CUDF_STRINGIFY(__LINE__) ": " reason) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure that we need the extra level of indirection of fail_unsupported
instead of just calling CUDF_FAIL
directly, but this looks fine to me.
Reworked the errors completely. Should be more informative now. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Discussed error handling offline. Future work can avoid testing for specific error messages, which was part of the motivation for wrapping the CUDF_FAIL macro in a common function.
@gpucibot merge |
Closes #9055
Limiting due to known nvcomp issues.