[jira] [Commented] (YARN-3528) Tests with 12345 as hard-coded port break jenkins

["Brahma Reddy Battula (JIRA)" <ji...@apache.org>]

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

Brahma Reddy Battula commented on YARN-3528:
--------------------------------------------

Thanks [~stevel@apache.org] and [~rkanter] for your inputs...Going to write one common utility where   
1) one method for "0" port,we can set back the port for same config
2)another method,As some places above one is not possible, we can use similiar way as [~rkanter] mentioned..

> Tests with 12345 as hard-coded port break jenkins
> -------------------------------------------------
>
>                 Key: YARN-3528
>                 URL: https://issues.apache.org/jira/browse/YARN-3528
>             Project: Hadoop YARN
>          Issue Type: Bug
>    Affects Versions: 3.0.0
>         Environment: ASF Jenkins
>            Reporter: Steve Loughran
>            Assignee: Brahma Reddy Battula
>            Priority: Blocker
>              Labels: test
>
> A lot of the YARN tests have hard-coded the port 12345 for their services to come up on.
> This makes it impossible to have scheduled or precommit tests to run consistently on the ASF jenkins hosts. Instead the tests fail regularly and appear to get ignored completely.
> A quick grep of "12345" shows up many places in the test suite where this practise has developed.
> * All {{BaseContainerManagerTest}} subclasses
> * {{TestNodeManagerShutdown}}
> * {{TestContainerManager}}
> + others
> This needs to be addressed through portscanning and dynamic port allocation. Please can someone do this.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)