Hadoop QA commented on YARN-3099:

{color:green}+1 overall{color}.  Here are the results of testing the latest 
  against trunk revision 1f2b695.

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

    {color:green}+1 tests included{color}.  The patch appears to include 3 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 

    {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/6425//console

This message is automatically generated.

> Capacity Scheduler LeafQueue/ParentQueue should use ResourceUsage to track 
> used-resources-by-label.
> ---------------------------------------------------------------------------------------------------
>                 Key: YARN-3099
>                 URL: https://issues.apache.org/jira/browse/YARN-3099
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: api, client, resourcemanager
>            Reporter: Wangda Tan
>            Assignee: Wangda Tan
>         Attachments: YARN-3099.1.patch
> After YARN-3092, resource-by-label (include 
> used-resource/pending-resource/reserved-resource/AM-resource, etc.) should be 
> tracked in ResourceUsage.
> To make each individual patch smaller to get easier review, this patch is 
> targeting to make used-resources-by-label in CS Queues are all tracked by 
> ResourceUsage.

This message was sent by Atlassian JIRA

Reply via email to