You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-dev@hadoop.apache.org by Apache Jenkins Server <je...@builds.apache.org> on 2013/09/18 07:31:38 UTC

Failed: YARN-5219 PreCommit Build #1953

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

###################################################################################
########################## LAST 60 LINES OF THE CONSOLE ###########################
Started by remote host 127.0.0.1
Building remotely on hadoop4 in workspace /home/jenkins/jenkins-slave/workspace/PreCommit-YARN-Build
Reverting /home/jenkins/jenkins-slave/workspace/PreCommit-YARN-Build/trunk to depth infinity with ignoreExternals: false
Updating http://svn.apache.org/repos/asf/hadoop/common/trunk at revision '2013-09-18T05:31:25.419 +0000'
At revision 1524295
Reverting /home/jenkins/jenkins-slave/workspace/PreCommit-YARN-Build/nightly to depth infinity with ignoreExternals: false
Updating http://svn.apache.org/repos/asf/hadoop/nightly at revision '2013-09-18T05:31:25.419 +0000'
At revision 1524295
no change for http://svn.apache.org/repos/asf/hadoop/common/trunk since the previous build
no change for http://svn.apache.org/repos/asf/hadoop/nightly since the previous build
No emails were triggered.
[PreCommit-YARN-Build] $ /bin/bash /tmp/hudson1649509658724048605.sh
32768
Running in Jenkins mode


======================================================================
======================================================================
    Testing patch for YARN-5219.
======================================================================
======================================================================


At revision 1524295.
YARN-5219 is not "Patch Available".  Exiting.


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


Archiving artifacts
Description set: YARN-5219
Recording test results
No test report files were found. Configuration error?
Build step 'Publish JUnit test result report' changed build result to FAILURE
Email was triggered for: Failure
Sending email for trigger: Failure



###################################################################################
############################## FAILED TESTS (if any) ##############################
No tests ran.

Success: YARN-1128 PreCommit Build #1955

Posted by Apache Jenkins Server <je...@builds.apache.org>.
Jira: https://issues.apache.org/jira/browse/YARN-1128
Build: https://builds.apache.org/job/PreCommit-YARN-Build/1955/

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

/bin/kill -9 8624 
kill: No such process
NOP




{color:green}+1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12603779/yarn-1128-1.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}.  The javadoc tool did not generate any 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: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/1955//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/1955//console

This message is automatically generated.


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


Comment added.
2eccec5f0a36c8f54d98b9ccb50c34602d992065 logged out


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


Archiving artifacts
Description set: YARN-1128
Recording test results
Email was triggered for: Success
Sending email for trigger: Success



###################################################################################
############################## FAILED TESTS (if any) ##############################
All tests passed

Failed: YARN-1089 PreCommit Build #1954

Posted by Apache Jenkins Server <je...@builds.apache.org>.
Jira: https://issues.apache.org/jira/browse/YARN-1089
Build: https://builds.apache.org/job/PreCommit-YARN-Build/1954/

###################################################################################
########################## LAST 60 LINES OF THE CONSOLE ###########################
[...truncated 3931 lines...]
{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12603755/YARN-1089.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 51 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}.  The javadoc tool did not generate any 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-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-tests hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site:

                  org.apache.hadoop.yarn.server.resourcemanager.scheduler.TestSchedulerUtils
                  org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.TestFairScheduler

                                      The following test timeouts occurred in hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-tests hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site:

org.apache.hadoop.mapreduce.v2.app.TestRMContainerAllocator

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

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

This message is automatically generated.


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


Comment added.
5318596ce94c3bd1d06bca9ddbb0bbc783603f68 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) ##############################
3 tests failed.
REGRESSION:  org.apache.hadoop.yarn.server.resourcemanager.scheduler.TestSchedulerUtils.testNormalizeRequestWithDominantResourceCalculator

Error Message:
expected:<<memory:1024, vCores:1, YCUs:720>> but was:<<memory:1024, vCores:-1, YCUs:1>>

Stack Trace:
java.lang.AssertionError: expected:<<memory:1024, vCores:1, YCUs:720>> but was:<<memory:1024, vCores:-1, YCUs:1>>
	at org.junit.Assert.fail(Assert.java:93)
	at org.junit.Assert.failNotEquals(Assert.java:647)
	at org.junit.Assert.assertEquals(Assert.java:128)
	at org.junit.Assert.assertEquals(Assert.java:147)
	at org.apache.hadoop.yarn.server.resourcemanager.scheduler.TestSchedulerUtils.testNormalizeRequestWithDominantResourceCalculator(TestSchedulerUtils.java:154)


REGRESSION:  org.apache.hadoop.yarn.server.resourcemanager.scheduler.TestSchedulerUtils.testValidateResourceRequest

Error Message:
More than max vcores should not be accepted

Stack Trace:
java.lang.AssertionError: More than max vcores should not be accepted
	at org.junit.Assert.fail(Assert.java:93)
	at org.apache.hadoop.yarn.server.resourcemanager.scheduler.TestSchedulerUtils.testValidateResourceRequest(TestSchedulerUtils.java:275)


REGRESSION:  org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.TestFairScheduler.testBackwardsCompatibleAllocationFileParsing

Error Message:
expected:<<memory:1024, vCores:1, YCUs:-1>> but was:<<memory:1024, vCores:1, YCUs:0>>

Stack Trace:
java.lang.AssertionError: expected:<<memory:1024, vCores:1, YCUs:-1>> but was:<<memory:1024, vCores:1, YCUs:0>>
	at org.junit.Assert.fail(Assert.java:93)
	at org.junit.Assert.failNotEquals(Assert.java:647)
	at org.junit.Assert.assertEquals(Assert.java:128)
	at org.junit.Assert.assertEquals(Assert.java:147)
	at org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.TestFairScheduler.testBackwardsCompatibleAllocationFileParsing(TestFairScheduler.java:913)