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

Rohith commented on YARN-2912:
------------------------------

Thanks Varun for updating patch. Approach looks good to me that rather all test 
fail,let only one test case fail.  
Some thought why this can appear randomly,
# As [~ste...@apache.org] said, it could be test case issue also.
# Operating Sysytem itself might have assigned this port to other process 
randomly.

In the patch, I see every test increment port by 10 which may result in test 
failure with same reason "address alredy  in use" because of other ports may be 
in use!!!
So possibility of test failures is more vulnerable all the time rather 1 time 
failure. Can we set port to 0 , so let OS takes available port. Any thoughts?
.

> 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
>             Fix For: 2.7.0
>
>         Attachments: YARN-2912.patch
>
>
> 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)

Reply via email to