Jira: https://issues.apache.org/jira/browse/YARN-2912 Build: https://builds.apache.org/job/PreCommit-YARN-Build/6025/
################################################################################### ########################## LAST 60 LINES OF THE CONSOLE ########################### [...truncated 4047 lines...] http://issues.apache.org/jira/secure/attachment/12685569/YARN-2912.patch against trunk revision 9297f98. {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:green}+1 tests included{color}. The patch appears to include 14 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:red}-1 core tests{color}. The patch failed these unit tests in hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-applicationhistoryservice hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager: org.apache.hadoop.yarn.server.resourcemanager.TestContainerResourceUsage {color:green}+1 contrib tests{color}. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-YARN-Build/6025//testReport/ Console output: https://builds.apache.org/job/PreCommit-YARN-Build/6025//console This message is automatically generated. ====================================================================== ====================================================================== Adding comment to Jira. ====================================================================== ====================================================================== Comment added. 3204e58764dd822ecfe0f4f9a5bc723412e4c5a9 logged out ====================================================================== ====================================================================== Finished build. ====================================================================== ====================================================================== Build step 'Execute shell' marked build as failure Archiving artifacts Sending artifact delta relative to PreCommit-YARN-Build #6024 Archived 30 artifacts Archive block size is 32768 Received 246 blocks and 1615168 bytes Compression is 83.3% Took 0.98 sec [description-setter] Could not determine description. Recording test results Email was triggered for: Failure Sending email for trigger: Failure ################################################################################### ############################## FAILED TESTS (if any) ############################## 3 tests failed. FAILED: org.apache.hadoop.yarn.server.resourcemanager.TestContainerResourceUsage.testUsageAfterAMRestartWithMultipleContainers Error Message: AppAttempt state is not correct (timedout) expected:<ALLOCATED> but was:<SCHEDULED> Stack Trace: java.lang.AssertionError: AppAttempt state is not correct (timedout) expected:<ALLOCATED> but was:<SCHEDULED> at org.junit.Assert.fail(Assert.java:88) at org.junit.Assert.failNotEquals(Assert.java:743) at org.junit.Assert.assertEquals(Assert.java:118) at org.apache.hadoop.yarn.server.resourcemanager.MockAM.waitForState(MockAM.java:86) at org.apache.hadoop.yarn.server.resourcemanager.MockRM.sendAMLaunched(MockRM.java:496) at org.apache.hadoop.yarn.server.resourcemanager.MockRM.launchAM(MockRM.java:661) at org.apache.hadoop.yarn.server.resourcemanager.MockRM.launchAndRegisterAM(MockRM.java:668) at org.apache.hadoop.yarn.server.resourcemanager.TestContainerResourceUsage.amRestartTests(TestContainerResourceUsage.java:272) at org.apache.hadoop.yarn.server.resourcemanager.TestContainerResourceUsage.testUsageAfterAMRestartWithMultipleContainers(TestContainerResourceUsage.java:251) FAILED: org.apache.hadoop.yarn.server.resourcemanager.TestContainerResourceUsage.testUsageWithOneAttemptAndOneContainer Error Message: AppAttempt state is not correct (timedout) expected:<ALLOCATED> but was:<SCHEDULED> Stack Trace: java.lang.AssertionError: AppAttempt state is not correct (timedout) expected:<ALLOCATED> but was:<SCHEDULED> at org.junit.Assert.fail(Assert.java:88) at org.junit.Assert.failNotEquals(Assert.java:743) at org.junit.Assert.assertEquals(Assert.java:118) at org.apache.hadoop.yarn.server.resourcemanager.MockAM.waitForState(MockAM.java:86) at org.apache.hadoop.yarn.server.resourcemanager.MockRM.sendAMLaunched(MockRM.java:496) at org.apache.hadoop.yarn.server.resourcemanager.TestContainerResourceUsage.testUsageWithOneAttemptAndOneContainer(TestContainerResourceUsage.java:97) FAILED: org.apache.hadoop.yarn.server.resourcemanager.TestContainerResourceUsage.testUsageAfterAMRestartKeepContainers Error Message: AppAttempt state is not correct (timedout) expected:<ALLOCATED> but was:<SCHEDULED> Stack Trace: java.lang.AssertionError: AppAttempt state is not correct (timedout) expected:<ALLOCATED> but was:<SCHEDULED> at org.junit.Assert.fail(Assert.java:88) at org.junit.Assert.failNotEquals(Assert.java:743) at org.junit.Assert.assertEquals(Assert.java:118) at org.apache.hadoop.yarn.server.resourcemanager.MockAM.waitForState(MockAM.java:86) at org.apache.hadoop.yarn.server.resourcemanager.MockRM.sendAMLaunched(MockRM.java:496) at org.apache.hadoop.yarn.server.resourcemanager.MockRM.launchAM(MockRM.java:661) at org.apache.hadoop.yarn.server.resourcemanager.MockRM.launchAndRegisterAM(MockRM.java:668) at org.apache.hadoop.yarn.server.resourcemanager.TestContainerResourceUsage.amRestartTests(TestContainerResourceUsage.java:272) at org.apache.hadoop.yarn.server.resourcemanager.TestContainerResourceUsage.testUsageAfterAMRestartKeepContainers(TestContainerResourceUsage.java:256)
