Remove PYTHONPATH variable from cudf tests - #368
Merged
Conversation
jolorunyomi
approved these changes
Oct 1, 2021
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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 PR removes the
PYTHONPATHvariable from thecudftest script that runs in ourdevelcontainers.The current value of this environment variable implies that
cudf(and associated libraries) are installed in-place (i.e. in the source repo itself). However, our currentcudfinstallation steps do not perform an in-place installation (as is evident by the missing-nflag in our install steps here). Instead,cudfis installed into thecondaenvironment which causes most of our tests to fail.In the future, we should update all of the libraries in our
develcontainers to perform an in-place install and add any necessaryPYTHONPATHvalues to the Docker container itself.