Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Wed, 22 Apr 2015 10:01:59 +0000 (UTC)
From: "Steve Loughran (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12822963.1429696911000.73278.1429696919590@Atlassian.JIRA>
In-Reply-To: <JIRA.12822963.1429696911000@Atlassian.JIRA>
References: <JIRA.12822963.1429696911000@Atlassian.JIRA>
 <JIRA.12822963.1429696911531@arcas>
Subject: [jira] [Created] (YARN-3528) Tests with 12345 as hard-coded port
 break jenkins
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Steve Loughran created YARN-3528:
------------------------------------

             Summary: 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
            Priority: Blocker


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)