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 2015/03/20 06:25:01 UTC
Failed: YARN-3126 PreCommit Build #7035
Jira: https://issues.apache.org/jira/browse/YARN-3126
Build: https://builds.apache.org/job/PreCommit-YARN-Build/7035/
###################################################################################
########################## LAST 60 LINES OF THE CONSOLE ###########################
[...truncated 3435 lines...]
{color:red}-1 overall{color}. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12697432/resourcelimit-02.patch
against trunk revision e37ca22.
{color:green}+1 @author{color}. The patch does not contain any @author tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include any new or modified tests.
Please justify why no new tests are needed for this patch.
Also please list what manual steps were performed to verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the total number of javac compiler warnings.
{color:red}-1 javadoc{color}. The javadoc tool appears to have generated 2 warning messages.
See https://builds.apache.org/job/PreCommit-YARN-Build/7035//artifact/patchprocess/diffJavadocWarnings.txt for details.
{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.
Test results: https://builds.apache.org/job/PreCommit-YARN-Build/7035//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/7035//console
This message is automatically generated.
======================================================================
======================================================================
Adding comment to Jira.
======================================================================
======================================================================
Comment added.
611e0bcf32f2f1c2c3425204cff0fdaa287d6ed2 logged out
======================================================================
======================================================================
Finished build.
======================================================================
======================================================================
Build step 'Execute shell' marked build as failure
Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #7033
Archived 20 artifacts
Archive block size is 32768
Received 52 blocks and 8894388 bytes
Compression is 16.1%
Took 2.7 sec
[description-setter] Could not determine description.
Recording test results
Email was triggered for: Failure
Sending email for trigger: Failure
###################################################################################
############################## FAILED TESTS (if any) ##############################
All tests passed
Failed: YARN-3382 PreCommit Build #7036
Posted by Apache Jenkins Server <je...@builds.apache.org>.
Jira: https://issues.apache.org/jira/browse/YARN-3382
Build: https://builds.apache.org/job/PreCommit-YARN-Build/7036/
###################################################################################
########################## LAST 60 LINES OF THE CONSOLE ###########################
[...truncated 3115 lines...]
cat: /home/jenkins/jenkins-slave/workspace/PreCommit-YARN-Build/../patchprocess/testrun_hadoop-yarn-server-resourcemanager.txt: No such file or directory
awk: cannot open /home/jenkins/jenkins-slave/workspace/PreCommit-YARN-Build/../patchprocess/testrun_hadoop-yarn-server-resourcemanager.txt (No such file or directory)
/home/jenkins/jenkins-slave/workspace/PreCommit-YARN-Build
{color:red}-1 overall{color}. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12705811/YARN-3382.patch
against trunk revision e37ca22.
{color:green}+1 @author{color}. The patch does not contain any @author tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include any new or modified tests.
Please justify why no new tests are needed for this patch.
Also please list what manual steps were performed to verify this patch.
{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.
Test results: https://builds.apache.org/job/PreCommit-YARN-Build/7036//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/7036//console
This message is automatically generated.
======================================================================
======================================================================
Adding comment to Jira.
======================================================================
======================================================================
Comment added.
f052f980a54856bde08340f0d2eb8ed6dea1e0e1 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) ##############################
All tests passed