Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Invalid
-
None
Description
This is similar to the symptoms seen in ARROW-11717 but it is still happening intermittently
On two separate PR I see similar failures:
https://github.com/apache/arrow/pull/9645/checks?check_run_id=2052183132
https://github.com/apache/arrow/pull/9647/checks?check_run_id=2051946608
Example failure:
subprocess.CalledProcessError: Command '['/build/cpp/debug/flight-test-integration-client', '-host', 'localhost', '-port=41743', '-scenario', 'auth:basic_proto']' died with <Signals.SIGABRT: 6>. During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/arrow/dev/archery/archery/integration/runner.py", line 308, in _run_flight_test_case consumer.flight_request(port, **client_args) File "/arrow/dev/archery/archery/integration/tester_cpp.py", line 116, in flight_request run_cmd(cmd) File "/arrow/dev/archery/archery/integration/util.py", line 148, in run_cmd raise RuntimeError(sio.getvalue()) RuntimeError: Command failed: /build/cpp/debug/flight-test-integration-client -host localhost -port=41743 -scenario auth:basic_proto With output: -------------- -- Arrow Fatal Error -- Invalid: Expected UNAUTHENTICATED but got Unavailable -------------- ################# FAILURES ################# FAILED TEST: auth:basic_proto Rust producing, C++ consuming
Attachments
Issue Links
- relates to
-
ARROW-11717 [Integration] Intermittent (but frequent) flight integration failures with auth:basic_proto
- Resolved
- links to