Update conda recipes for Enhanced Compatibility effort
#164
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
ajschmidt8
added
improvement
raydouglass
approved these changes
Nov 22, 2021
|
@gpucibot merge |
jolorunyomi
approved these changes
Nov 22, 2021
|
rerun tests |
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.
Similar to rapidsai/cudf#9456.
This PR updates the
condarecipe build strings andcudatoolkitversion specifications as part of the Enhanced Compatibility efforts.The build strings have been updated to only include the major CUDA version (i.e.
librmm-21.12.00a-cuda11_gc781527_12.tar.bz2) and thecudatoolkitversion specifications will now be formatted likecudatoolkit >=x,<y.0a0(i.e.cudatoolkit >=11,<12.0a0).Moving forward, we'll build the packages with a single CUDA version (i.e.
11.5) and test them in environments with different CUDA versions (i.e.11.0,11.2,11.4,11.5etc.).