Hadoop QA commented on YARN-3383:

{color:red}-1 overall{color}.  Here are the results of testing the latest 
  against trunk revision 972f1f1.

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

    {color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
                        Please justify why no new tests are needed for this 
                        Also please list what manual steps were performed to 
verify this patch.

    {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 

    {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 

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

This message is automatically generated.

> AdminService should use "warn" instead of "info" to log exception when 
> operation fails
> --------------------------------------------------------------------------------------
>                 Key: YARN-3383
>                 URL: https://issues.apache.org/jira/browse/YARN-3383
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: resourcemanager
>            Reporter: Wangda Tan
>            Assignee: Li Lu
>         Attachments: YARN-3383-032015.patch, YARN-3383-032315.patch
> Now it uses info:
> {code}
>   private YarnException logAndWrapException(IOException ioe, String user,
>       String argName, String msg) throws YarnException {
>     LOG.info("Exception " + msg, ioe);
> {code}
> But it should use warn instead.

This message was sent by Atlassian JIRA

Reply via email to