[
https://issues.apache.org/jira/browse/ARROW-8176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wes McKinney resolved ARROW-8176.
---------------------------------
Fix Version/s: 0.17.0
Resolution: Fixed
Issue resolved by pull request 6693
[https://github.com/apache/arrow/pull/6693]
> [FlightRPC][Integration] Have Flight services bind to port 0 in integration
> ---------------------------------------------------------------------------
>
> Key: ARROW-8176
> URL: https://issues.apache.org/jira/browse/ARROW-8176
> Project: Apache Arrow
> Issue Type: Bug
> Components: FlightRPC, Integration
> Reporter: David Li
> Assignee: David Li
> Priority: Major
> Labels: pull-request-available
> Fix For: 0.17.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> 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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
