[ARROW-6528] [C++] Spurious Flight test failures (port allocation failure)

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.17.0
• Component/s: C++
• External issue URL: https://github.com/apache/arrow/issues/22893
• Assignee: David Li
• Reporter: Antoine Pitrou
• Created: 11/Sep/19 13:27
• Updated: 11/Jan/23 07:47
• Resolved: 27/Mar/20 20:49

Description

Seems like our port allocation scheme inside unit tests is still not very reliable :-/
https://ci.ursalabs.org/#/builders/71/builds/4147/steps/8/logs/stdio

[----------] 3 tests from TestMetadata
[ RUN      ] TestMetadata.DoGet
E0905 12:45:40.322644527   10203 server_chttp2.cc:40]        {"created":"@1567687540.322612245","description":"No address added out of total 1 resolved","file":"../src/core/ext/transport/chttp2/server/chttp2_server.cc","file_line":394,"referenced_errors":[{"created":"@1567687540.322609844","description":"Unable to configure socket","fd":7,"file":"../src/core/lib/iomgr/tcp_server_utils_posix_common.cc","file_line":217,"referenced_errors":[{"created":"@1567687540.322602634","description":"Address already in use","errno":98,"file":"../src/core/lib/iomgr/tcp_server_utils_posix_common.cc","file_line":190,"os_error":"Address already in use","syscall":"bind"}]}]}
../src/arrow/flight/flight_test.cc:429: Failure
Failed
'server->Init(options)' failed with Unknown error: Server did not start properly
/buildbot/AMD64_Conda_Python_3_7/cpp/build-support/run-test.sh: line 97: 10203 Segmentation fault      (core dumped) $TEST_EXECUTABLE "$@" 2>&1
     10204 Done                    | $ROOT/build-support/asan_symbolize.py
     10205 Done                    | ${CXXFILT:-c++filt}
     10206 Done                    | $ROOT/build-support/stacktrace_addr2line.pl $TEST_EXECUTABLE
     10207 Done                    | $pipe_cmd 2>&1
     10208 Done                    | tee $LOGFILE
/buildbot/AMD64_Conda_Python_3_7/cpp/build/src/arrow/flight

Issue Links

• is related to: ARROW-8176 [FlightRPC][Integration] Have Flight services bind to port 0 in integration