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

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.17.0
• Component/s: FlightRPC, Integration
• Labels: pull-request-available
• External issue URL: https://github.com/apache/arrow/issues/24377
• Assignee: David Li
• Reporter: David Li
• Created: 20/Mar/20 18:18
• Updated: 11/Jan/23 07:58
• Resolved: 24/Mar/20 19:54

Description

In integration tests, instead of allocating a port and then trying to bind to it, we should have the Flight server bind to port 0, then have the test runner parse out the port. This avoids flakiness due to port collisions. This also will give us the ability to know when the Flight server has actually started.

Issue Links

• relates to: ARROW-6528 [C++] Spurious Flight test failures (port allocation failure)
• links to: GitHub Pull Request #6693