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

Hadoop QA commented on YARN-2810:
---------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12679571/apche-yarn-2810.0.patch
  against trunk revision a7fbd4e.

    {color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

    {color:green}+1 tests included{color}.  The patch appears to include 1 new 
or modified test files.

    {color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

    {color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

    {color:green}+1 eclipse:eclipse{color}.  The patch built with 
eclipse:eclipse.

    {color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 2.0.3) warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager.

    {color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-YARN-Build/5738//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5738//console

This message is automatically generated.

> TestRMProxyUsersConf fails on Windows VMs
> -----------------------------------------
>
>                 Key: YARN-2810
>                 URL: https://issues.apache.org/jira/browse/YARN-2810
>             Project: Hadoop YARN
>          Issue Type: Test
>          Components: resourcemanager
>            Reporter: Varun Vasudev
>            Assignee: Varun Vasudev
>         Attachments: apche-yarn-2810.0.patch
>
>
> TestRMProxyUsersConf fails on Windows VMs. The root cause is that 
> InetAddress.getHostName() and InetAddress.getCanonicalHostName() can return 
> ips if DNS lookups fail.



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

Reply via email to