Jira: https://issues.apache.org/jira/browse/YARN-1811
Build: https://builds.apache.org/job/PreCommit-YARN-Build/3318/

###################################################################################
########################## LAST 60 LINES OF THE CONSOLE 
###########################
[...truncated 3223 lines...]
NOP




{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12633842/YARN-1811.patch
  against trunk revision .

    {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 1.3.9) 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-resourcemanager:

                  
org.apache.hadoop.yarn.server.resourcemanager.TestFifoScheduler

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

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

This message is automatically generated.


======================================================================
======================================================================
    Adding comment to Jira.
======================================================================
======================================================================


Comment added.
538c7aa9e00f9d81874812ee8db52364ed173ce6 logged out


======================================================================
======================================================================
    Finished build.
======================================================================
======================================================================


Build step 'Execute shell' marked build as failure
Archiving artifacts
[description-setter] Could not determine description.
Recording test results
Email was triggered for: Failure
Sending email for trigger: Failure



###################################################################################
############################## FAILED TESTS (if any) 
##############################
1 tests failed.
REGRESSION:  
org.apache.hadoop.yarn.server.resourcemanager.TestFifoScheduler.testNonDefaultMinimumAllocation

Error Message:
AppAttempt state is not correct (timedout) expected:<ALLOCATED> but 
was:<SCHEDULED>

Stack Trace:
junit.framework.AssertionFailedError: AppAttempt state is not correct 
(timedout) expected:<ALLOCATED> but was:<SCHEDULED>
        at junit.framework.Assert.fail(Assert.java:50)
        at junit.framework.Assert.failNotEquals(Assert.java:287)
        at junit.framework.Assert.assertEquals(Assert.java:67)
        at 
org.apache.hadoop.yarn.server.resourcemanager.MockAM.waitForState(MockAM.java:82)
        at 
org.apache.hadoop.yarn.server.resourcemanager.MockRM.sendAMLaunched(MockRM.java:368)
        at 
org.apache.hadoop.yarn.server.resourcemanager.TestFifoScheduler.testMinimumAllocation(TestFifoScheduler.java:198)
        at 
org.apache.hadoop.yarn.server.resourcemanager.TestFifoScheduler.testNonDefaultMinimumAllocation(TestFifoScheduler.java:228)


Reply via email to