CI: Fix pyarrow compat #23266
Closed
CI: Fix pyarrow compat #23266
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
|
Hello @jbrockmendel! Thanks for updating the PR.
Comment last updated on October 21, 2018 at 21:13 Hours UTC |
|
there is already another PR with this change |
|
Great, closing in favor of #23112. |
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.
It looks like the last couple days of CI failures are caused by pyarrow (required by feather-format) bumping from 0.9.0 to 0.11.0. This checks the version and adapts the passed kwarg as appropriate.
Do we need to pin pyarrow in the CI config to make sure both versions are tested?