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

Yu Li commented on FLINK-11888:
-------------------------------

[~sunjincheng121] has located the root cause of the port conflict issue in 
FLINK-11892 and will contain the change required there in the document 
refinement.

> Refine document of how to run end-to-end tests
> ----------------------------------------------
>
>                 Key: FLINK-11888
>                 URL: https://issues.apache.org/jira/browse/FLINK-11888
>             Project: Flink
>          Issue Type: Improvement
>          Components: Documentation, Tests
>            Reporter: Yu Li
>            Assignee: Yu Li
>            Priority: Major
>
> End-to-end tests are included in the scope of verifying a Flink release from 
> [document|https://cwiki.apache.org/confluence/display/FLINK/Verifying+a+Flink+Release],
>  and following the [read 
> me|https://github.com/apache/flink/tree/master/flink-end-to-end-tests] on 
> github to verify the nightly tests, I found several things need to be 
> clarified, especially on a clean environment (never run nightly tests 
> before), including:
> * We should clarify where to find the "<flink dir>" to run the tests against
> * We should clarify what preparation required before run the "Kerberized YARN 
> on Docker test", if user choose to.
> Besides, I've observed some test failure caused by port occupation like below 
> (probably due to resource release failure of completed tests) but it seems to 
> be environment-related (checked against 4 macbook, 3 with stable failure and 
> 1 success; checked against 2 linux vm, 1 with stable failure and 1 success). 
> Will dig more and add to the document if any environment cleanup/set 
> required, or open another JIRA if any improvement needed for the scripts.
> {noformat}
> java.net.BindException: Could not start actor system on any port in port 
> range 6123
> {noformat}



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

Reply via email to