[
https://issues.apache.org/jira/browse/YARN-3265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14340630#comment-14340630
]
Hadoop QA commented on YARN-3265:
---------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12701412/YARN-3265.2.patch
against trunk revision 01a1621.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 8 new
or modified test files.
{color:red}-1 javac{color:red}. The patch appears to cause the build to
fail.
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/6782//console
This message is automatically generated.
> CapacityScheduler deadlock when computing absolute max avail capacity (fix
> for trunk/branch-2)
> ----------------------------------------------------------------------------------------------
>
> Key: YARN-3265
> URL: https://issues.apache.org/jira/browse/YARN-3265
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: capacityscheduler, resourcemanager
> Reporter: Wangda Tan
> Assignee: Wangda Tan
> Priority: Blocker
> Attachments: YARN-3265.1.patch, YARN-3265.2.patch
>
>
> This patch is trying to solve the same problem described in YARN-3251, but
> this is a longer term fix for trunk and branch-2.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
