[ 
https://issues.apache.org/jira/browse/FLINK-4052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16651194#comment-16651194
 ] 

ASF GitHub Bot commented on FLINK-4052:
---------------------------------------

leanken edited a comment on issue #6853: [FLINK-4052] using non-local 
unreachable ip:port to fix unstable Test 
testReturnLocalHostAddressUsingHeuristics
URL: https://github.com/apache/flink/pull/6853#issuecomment-430116056
 
 
   cc @tillrohrmann 
   Saw a couple of issue relate to testReturnLocalHostAddressUsingHeuristics 
unstable failure. Here is my diagnose procedure and proposal to fix this 
unstable case. 

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Unstable test ConnectionUtilsTest
> ---------------------------------
>
>                 Key: FLINK-4052
>                 URL: https://issues.apache.org/jira/browse/FLINK-4052
>             Project: Flink
>          Issue Type: Bug
>          Components: Tests
>    Affects Versions: 1.0.2, 1.3.0
>            Reporter: Stephan Ewen
>            Assignee: Stephan Ewen
>            Priority: Critical
>              Labels: pull-request-available, test-stability
>             Fix For: 1.7.0, 1.6.2, 1.5.5
>
>
> The error is the following:
> {code}
> ConnectionUtilsTest.testReturnLocalHostAddressUsingHeuristics:59 
> expected:<testing-worker-linux-docker-e744e561-3361-linux-13/172.17.5.9> but 
> was:</127.0.0.1>
> {code}
> The probable cause for the failure is that the test tries to select an unused 
> closed port (from the ephemeral range), and then assumes that all connections 
> to that port fail.
> If a concurrent test actually uses that port, connections to the port will 
> succeed.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to