[jira] [Commented] (YARN-2316) TestNMWebServices* get failed on trunk
[ https://issues.apache.org/jira/browse/YARN-2316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14068628#comment-14068628 ] Tsuyoshi OZAWA commented on YARN-2316: -- Close this as dup off YARN-2304, because the cause of YARN-2304, YARN-2316, MAPREDUCE-5973 look same. Let's consolidate them and deal with on YARN-2304. TestNMWebServices* get failed on trunk -- Key: YARN-2316 URL: https://issues.apache.org/jira/browse/YARN-2316 Project: Hadoop YARN Issue Type: Bug Components: nodemanager Reporter: Junping Du From Jenkins test in YARN-2045 and YARN-1341, these tests get failed with address already get bind. The similar issue happens at RMWebService (YARN-2304) and AMWebService (MAPREDUCE-5973) as well. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (YARN-2316) TestNMWebServices* get failed on trunk
[ https://issues.apache.org/jira/browse/YARN-2316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14069593#comment-14069593 ] Junping Du commented on YARN-2316: -- +1 on resolving it as duplicated. It looks like these failures are all for the same reason. TestNMWebServices* get failed on trunk -- Key: YARN-2316 URL: https://issues.apache.org/jira/browse/YARN-2316 Project: Hadoop YARN Issue Type: Bug Components: nodemanager Reporter: Junping Du From Jenkins test in YARN-2045 and YARN-1341, these tests get failed with address already get bind. The similar issue happens at RMWebService (YARN-2304) and AMWebService (MAPREDUCE-5973) as well. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (YARN-2316) TestNMWebServices* get failed on trunk
[ https://issues.apache.org/jira/browse/YARN-2316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14067460#comment-14067460 ] Tsuyoshi OZAWA commented on YARN-2316: -- Hi [~djp], I think there are two kind of possibility - 1. new added tests recently on Web-Services didn't do proper cleanup as you mentioned 2. infra change for Jenkins CI influences and the problem appear. As I mentioned on YARN-2304, we don't support parallel test now because JerseyTest 1.9 doesn't support it. If the test run in parallel on single machine, it goes fail. TestNMWebServices* get failed on trunk -- Key: YARN-2316 URL: https://issues.apache.org/jira/browse/YARN-2316 Project: Hadoop YARN Issue Type: Bug Components: nodemanager Reporter: Junping Du From Jenkins test in YARN-2045 and YARN-1341, these tests get failed with address already get bind. The similar issue happens at RMWebService (YARN-2304) and AMWebService (MAPREDUCE-5973) as well. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (YARN-2316) TestNMWebServices* get failed on trunk
[ https://issues.apache.org/jira/browse/YARN-2316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14065705#comment-14065705 ] Junping Du commented on YARN-2316: -- I suspect some new added tests recently on Web-Services didn't do proper cleanup. TestNMWebServices* get failed on trunk -- Key: YARN-2316 URL: https://issues.apache.org/jira/browse/YARN-2316 Project: Hadoop YARN Issue Type: Bug Components: nodemanager Reporter: Junping Du From Jenkins test in YARN-2045 and YARN-1341, these tests get failed with address already get bind. The similar issue happens at RMWebService (YARN-2304) and AMWebService (MAPREDUCE-5973) as well. -- This message was sent by Atlassian JIRA (v6.2#6252)
