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

Hadoop QA commented on HADOOP-8238:
-----------------------------------

+1 overall.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12520843/hadoop-8238.txt
  against trunk revision .

    +1 @author.  The patch does not contain any @author tags.

    +1 tests included.  The patch appears to include 3 new or modified tests.

    +1 javadoc.  The javadoc tool did not generate any warning messages.

    +1 javac.  The applied patch does not increase the total number of javac 
compiler warnings.

    +1 eclipse:eclipse.  The patch built with eclipse:eclipse.

    +1 findbugs.  The patch does not introduce any new Findbugs (version 1.3.9) 
warnings.

    +1 release audit.  The applied patch does not increase the total number of 
release audit warnings.

    +1 core tests.  The patch passed unit tests in .

    +1 contrib tests.  The patch passed contrib unit tests.

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

This message is automatically generated.
                
> NetUtils#getHostNameOfIP blows up if given ip:port string w/o port
> ------------------------------------------------------------------
>
>                 Key: HADOOP-8238
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8238
>             Project: Hadoop Common
>          Issue Type: Bug
>            Reporter: Eli Collins
>            Assignee: Eli Collins
>         Attachments: hadoop-8238.txt
>
>
> NetUtils#getHostNameOfIP blows up if not given a string of form ip:port, 
> because the regex matches the port optionally but the code requires a 
> semicolon. It also doesn't check the given string for null.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to