Hadoop QA commented on YARN-2876:

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

    {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 

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

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

This message is automatically generated.

> In Fair Scheduler, JMX and Scheduler UI display wrong maxResource info for 
> subqueues
> ------------------------------------------------------------------------------------
>                 Key: YARN-2876
>                 URL: https://issues.apache.org/jira/browse/YARN-2876
>             Project: Hadoop YARN
>          Issue Type: Bug
>            Reporter: Siqi Li
>            Assignee: Siqi Li
>         Attachments: YARN-2876.v1.patch, screenshot-1.png
> If a subqueue doesn't have a maxResource set in fair-scheduler.xml, JMX and 
> Scheduler UI will display the entire cluster capacity as its maxResource 
> instead of its parent queue's maxResource.

This message was sent by Atlassian JIRA

Reply via email to