hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brahma Reddy Battula (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-3528) Tests with 12345 as hard-coded port break jenkins
Date Fri, 19 Jun 2015 16:23:01 GMT

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

Brahma Reddy Battula commented on YARN-3528:

[~varun_saxena] thanks for looking into this issue.Attached the patch to address almost all
the comments.

{quote}As this is a utility class which might be used elsewhere as well, can we pass an initial
port into getPort() and try with that port first before randomizing . We can use this instead
of using 49152 everytime.{quote}
Sounds good to me..

> 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
>         Attachments: YARN-3528-002.patch, YARN-3528.patch
> A lot of the YARN tests have hard-coded the port 12345 for their services to come up
> 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
> * 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

View raw message