[ https://issues.apache.org/jira/browse/YARN-2638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14156019#comment-14156019 ]
Hadoop QA commented on YARN-2638: --------------------------------- {color:green}+1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12672476/YARN-2638-1.patch against trunk revision 9e40de6. {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:green}+1 tests included{color}. The patch appears to include 1 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 eclipse:eclipse. {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 hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager. {color:green}+1 contrib tests{color}. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-YARN-Build/5230//testReport/ Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5230//console This message is automatically generated. > Let TestRM run with all types of schedulers (FIFO, Capacity, Fair) > ------------------------------------------------------------------ > > Key: YARN-2638 > URL: https://issues.apache.org/jira/browse/YARN-2638 > Project: Hadoop YARN > Issue Type: Bug > Reporter: Wei Yan > Assignee: Wei Yan > Attachments: YARN-2638-1.patch > > > TestRM fails when using FairScheduler or FifoScheduler. The failures not > shown in trunk as the trunk uses the default capacity scheduler. We need to > let TestRM run with all types of schedulers, to make sure any new change > wouldn't break any scheduler. -- This message was sent by Atlassian JIRA (v6.3.4#6332)