hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-2912) Jersey Tests failing with port in use
Date Sun, 30 Nov 2014 17:09:12 GMT

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

Steve Loughran commented on YARN-2912:
--------------------------------------

scanning for a clear port isn't that slow, it just adds complexity

One question is : why is this test failing  now? It could be that a previous instance didn't
get cleaned up, in which case finding and fixing the leakage may be a strategy. 

Simply using a (rolling) increment may work well most of the time, and ensures that if a port
is blocked, only a single test will fail, rather than all of them. Why don't we start with
that and then see how well it goes

> Jersey Tests failing with port in use
> -------------------------------------
>
>                 Key: YARN-2912
>                 URL: https://issues.apache.org/jira/browse/YARN-2912
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: test
>    Affects Versions: 3.0.0
>         Environment: jenkins on java 8
>            Reporter: Steve Loughran
>            Assignee: Varun Saxena
>
> Jersey tests like TestNMWebServices apps are failing with port in use.
> The jersey test runner appears to always use the same port unless a system property is
set to point to a different one. Every test should really be changing that sysprop in a @Before
method



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

Mime
View raw message