[ARROW-16053] [C++][FlightRPC] Fix flaky test TestAuthHandler.FailUnauthenticatedCalls

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 8.0.0
• Component/s: C++, FlightRPC
• Labels: pull-request-available
• External issue URL: https://github.com/apache/arrow/issues/31471
• Assignee: David Li
• Reporter: David Li
• Created: 29/Mar/22 00:21
• Updated: 11/Jan/23 14:41
• Resolved: 30/Mar/22 16:32

Description

[ 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 

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.

Issue Links

• links to: GitHub Pull Request #12748