Add environment variable definitions to run the nanoarrow integration tests #5764
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
paleolimbot
changed the title
|
The intention wasn't necessarily to run them, but rather to have the CI tests actually run - there doesn't appear to be a way to not build nanoarrow 😆 That being said, if we can test against nanoarrow it can't hurt to do so 😄 |
|
I see! To do that you'd have to set |
|
Thank you |
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.
Which issue does this PR close?
Closes #5763.
Rationale for this change
It seems that the intention was to run nanoarrow's integration test suite (thanks!); however, the tests were not running.
What changes are included in this PR?
The requisite environment variable definitions were added for the tests to run.
Are there any user-facing changes?
No!