h-vetinari commented on issue #35587: URL: https://github.com/apache/arrow/issues/35587#issuecomment-1835413633
Rebased https://github.com/conda-forge/arrow-cpp-feedstock/pull/1058 on arrow 14 and added minio. Still failing a couple tests, here for linux: ``` The following tests FAILED: 34 - arrow-utility-test (Failed) 68 - arrow-gcsfs-test (Failed) 69 - arrow-s3fs-test (Failed) ``` `arrow-gcsfs-test` is expected due to not having `testbench` (see above), so that's less of an issue ATM. For `arrow-utility-test`, we have a single failure: ``` [ RUN ] TimestampParser.StrptimeZoneOffset $SRC_DIR/cpp/src/arrow/util/value_parsing_test.cc:811: Failure Expected equality of these values: expected Which is: 1514769420 converted Which is: 1514769408 Google Test trace: $SRC_DIR/cpp/src/arrow/util/value_parsing_test.cc:806: 2018-01-01 00:00:00-0117 [ FAILED ] TimestampParser.StrptimeZoneOffset (0 ms) ``` which -- based on the values -- kinda looks like it's a question of leap seconds being applied or not (though the -0117 "time zone" looks very weird too). Not sure if this needs a newer linux distro than we're running...? While `arrow-s3fs-test` can now call `minio`, it still fails pretty much all tests that call it AFAICT, for example: ``` [ RUN ] TestS3FS.CreateDir $SRC_DIR/cpp/src/arrow/filesystem/s3fs_test.cc:919: Failure Failed Expected 'fs_->CreateDir("bucket/somefile")' to fail with IOError, but got OK [ FAILED ] TestS3FS.CreateDir (84 ms) [ RUN ] TestS3FSGeneric.DeleteDir $SRC_DIR/cpp/src/arrow/filesystem/test_util.cc:77: Failure Expected equality of these values: paths Which is: { "AB", "AB/CD", "AB/CD/EF", "AB/GH" } expected_paths Which is: { "AB", "AB/GH" } [ FAILED ] TestS3FSGeneric.DeleteDir (78 ms) ``` This might be related to the fact that we only have a newer minio in conda-forge than what arrow uses (see https://github.com/apache/arrow/issues/37692). Though I also see ``` WARNING: MINIO_ACCESS_KEY and MINIO_SECRET_KEY are deprecated. Please use MINIO_ROOT_USER and MINIO_ROOT_PASSWORD ``` so it could be something related to not having some AWS dummy account somewhere to perform operations on? There's more errors on the CUDA builds (which presumably try to look for a GPU and fail), but that's not the first priority now. On OSX, we get: ``` The following tests FAILED: 68 - arrow-gcsfs-test (Failed) 69 - arrow-s3fs-test (Failed) ``` In particular, the `arrow-utility-test` does not fail like on linux. On windows, we have more failures: ``` The following tests FAILED: 18 - arrow-compute-scalar-cast-test (Failed) 21 - arrow-compute-scalar-temporal-test (Failed) 64 - arrow-dataset-file-orc-test (Failed) 68 - arrow-gcsfs-test (Failed) 69 - arrow-s3fs-test (Failed) 80 - arrow-orc-adapter-test (Failed) 81 - arrow-substrait-substrait-test (Failed) 91 - gandiva-internals-test (Failed) 100 - gandiva-date-time-test (Failed) ``` Here's a link to the [CI run](https://dev.azure.com/conda-forge/feedstock-builds/_build/results?buildId=834256&view=results). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
