Revert "Enable testing zstd for spark releases 3.2.0 and later (#5898)" #5916
Conversation
This file contains 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
|
Closes #5914 |
|
build |
sameerz
added
the
task
jlowe
approved these changes
Jun 27, 2022
This was referenced Jul 12, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This reverts commit 321f9b9.
Signed-off-by: Jim Brennan jimb@nvidia.com
I jumped the gun on putting in #5898. It currently requires setting an environment variable to work.
LIBCUDF_NVCOMP_POLICY=ALWAYS. I don't think it is appropriate to set this in the unit tests, because it could cause the use of experimental releases in the future.
I am reverting this now and will bring it back once ZSTD is available with the default of LIBCUDF_NVCOMP_POLICY=STABLE.