h-vetinari commented on issue #35587:
URL: https://github.com/apache/arrow/issues/35587#issuecomment-2452888609

   I updated https://github.com/conda-forge/arrow-cpp-feedstock/pull/1058 for 
v18, opened a [PR](https://github.com/apache/arrow/pull/44621) for the failure 
of `TimestampParser.StrptimeZoneOffset` with old glibc (and backported that), 
skipped the gcsfs tests (which cannot pass without 
[testbench](https://github.com/googleapis/storage-testbench)) and what I'm 
getting with all that is that windows and osx are passing (🥳), while on linux 
there are two failures:
   
   ```
   The following tests FAILED:
         43 - arrow-csv-test (Failed)
         76 - arrow-flight-test (Failed)
   ```
   In more detail:
   ```
   [ RUN      ] TimestampConversion.UserDefinedParsersWithZone
   $SRC_DIR/cpp/src/arrow/csv/converter_test.cc:169: Failure
   Failed
   Expected 'converter->Convert(*parser, i)' to fail with Invalid, but got OK
   
   $SRC_DIR/cpp/src/arrow/csv/converter_test.cc:169: Failure
   Failed
   Expected 'converter->Convert(*parser, i)' to fail with Invalid, but got OK
   
   [  FAILED  ] TimestampConversion.UserDefinedParsersWithZone (0 ms)
   ```
   (this is potentially due to https://github.com/apache/arrow/pull/44621, as I 
haven't seen it before)
   
   The more serious one is the flight test, which just crashes/aborts
   ```
   [----------] 3 tests from GrpcAsyncClientTest
   [ RUN      ] GrpcAsyncClientTest.TestGetFlightInfo
   [       OK ] GrpcAsyncClientTest.TestGetFlightInfo (3 ms)
   [ RUN      ] GrpcAsyncClientTest.TestGetFlightInfoFuture
   WARNING: All log messages before absl::InitializeLog() is called are written 
to STDERR
   E0000 00:00:1730526628.609332   29678 thd.cc:184] pthread_join failed: 
Resource deadlock avoided
   
~/feedstock_root/build_artifacts/apache-arrow_1730522866415/work/cpp/build/src/arrow/flight
   ```
   


-- 
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]

Reply via email to