David Li created ARROW-16053:
--------------------------------
Summary: [C++][FlightRPC] Fix flaky test
TestAuthHandler.FailUnauthenticatedCalls
Key: ARROW-16053
URL: https://issues.apache.org/jira/browse/ARROW-16053
Project: Apache Arrow
Issue Type: Improvement
Components: C++, FlightRPC
Reporter: David Li
Assignee: David Li
{noformat}
[ RUN ] TestAuthHandler.FailUnauthenticatedCalls
C:/projects/arrow/cpp/src/arrow/flight/flight_test.cc(1103): error: Failed
'status' failed with IOError: Could not write record batch to stream (server
disconnect?). Detail: Internal
C:/projects/arrow/cpp/src/arrow/flight/client.cc:362: Close() failed: IOError:
gRPC returned unauthenticated error, with message: Invalid token. Detail:
Unauthenticated. gRPC client debug context:
{"created":"@1648486690.229000000","description":"Error received from peer
ipv6:[::1]:2265","file":"D:\bld\grpc-cpp_1646464801475\work\src\core\lib\surface\call.cc","file_line":904,"grpc_message":"Invalid
token. Detail: Unauthenticated","grpc_status":16}. Client context: OK. Detail:
Unauthenticated {noformat}
Depending on whether gRPC queues the write or not, the write call may or may
not fail (or it may fail with an unexpected error), we need to account for
these cases.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
