-
-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enable test suite of libarrow
#1058
Conversation
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( |
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( |
26074b3
to
afb81ea
Compare
) ### Rationale for this change Enable tests for libarrow in conda-forge: #35587 ### What changes are included in this PR? old glibc does not actually support timezones like `-0117` (used in `StrptimeZoneOffset` test). The exact lower bound for glibc is hard for me to determine; I know that it passes with 2.28 and that it fails with 2.17. Anything in between is an open question. I went with the conservative option here. ### Are these changes tested? Tested in conda-forge/arrow-cpp-feedstock#1058 ### Are there any user-facing changes? * GitHub Issue: #43808 Lead-authored-by: H. Vetinari <[email protected]> Co-authored-by: Sutou Kouhei <[email protected]> Signed-off-by: Sutou Kouhei <[email protected]>
except those depending on timing, following upstream, see https://github.com/apache/arrow/blob/apache-arrow-12.0.0/ci/appveyor-cpp-build.bat#L63-L68
also requires git submodule for parquet test data
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( I do have some suggestions for making it better though... For recipe/meta.yaml:
This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/12000178104. Examine the logs at this URL for more detail. |
cannot run test suite without an actual GPU
libarrow
libarrow
Alrighty, after over 2 years of working towards this, we now have the C++ tests running for |
Enable test suite of `libarrow`
Since #875, we're now running with the test suite for
pyarrow
. While working on #1048, I wanted to ensure that also the library portion works as intended, so thought about switching on the test suite forlibarrow
.After some initial attempts it looks like this is failing, hence will need some iteration together with upstream.