Fix pip install issue on CI
#4310
Merged
Conversation
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
Member
Author
|
cc @dask/maintenance |
jrbourbeau
approved these changes
Dec 3, 2020
Member
jrbourbeau
left a comment
jrbourbeau
left a comment
There was a problem hiding this comment.
This seems totally sensible, especially if it fixes CI failures. Will merge once CI finishes
Member
Author
|
Thanks James! 😄 |
Member
|
Hmm FWIW it looks like we may still be experiencing this |
Member
Author
|
Was also seeing that until rebasing on latest |
Member
Author
|
Provided a more detailed response here ( #4313 (comment) ). HTH |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Fixes an issue we are seeing on CI. This came up for us in RAPIDS and this solved the issue there as well. Basically
pip's solver seems to be trying to get involved here even though we don't need it to. Specifying the repo branches seems to bypass the issue.This also came up in dask-cloudprovider recently ( dask/dask-cloudprovider#203 ).