You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tez.apache.org by Apache Jenkins Server <je...@builds.apache.org> on 2017/08/09 21:43:05 UTC
Failed: TEZ-3159 PreCommit Build #2608
Jira: https://issues.apache.org/jira/browse/TEZ-3159
Build: https://builds.apache.org/job/PreCommit-TEZ-Build/2608/
###################################################################################
########################## LAST 60 LINES OF THE CONSOLE ###########################
[...truncated 111.79 KB...]
Running tests
/home/jenkins/tools/maven/latest/bin/mvn clean install -fn -DTezPatchProcess
cat: /home/jenkins/jenkins-slave/workspace/PreCommit-TEZ-Build@2/../patchprocess/testrun.txt: No such file or directory
awk: cannot open /home/jenkins/jenkins-slave/workspace/PreCommit-TEZ-Build@2/../patchprocess/testrun.txt (No such file or directory)
{color:green}+1 overall{color}. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12881071/TEZ-3159.002.patch
against master revision 8dcf8a1.
{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 findbugs{color}. The patch does not introduce any new Findbugs (version 3.0.1) 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 .
Test results: https://builds.apache.org/job/PreCommit-TEZ-Build/2608//testReport/
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/2608//console
This message is automatically generated.
======================================================================
======================================================================
Adding comment to Jira.
======================================================================
======================================================================
Comment added.
e62c680fd4763289a8719ca5fdec3d5345a170eb logged out
======================================================================
======================================================================
Finished build.
======================================================================
======================================================================
Archiving artifacts
ERROR: No artifacts found that match the file pattern "patchprocess/*.*". Configuration error?
ERROR: ?patchprocess/*.*? doesn?t match anything, but ?*.*? does. Perhaps that?s what you mean?
Build step 'Archive the artifacts' changed build result to FAILURE
[description-setter] Could not determine description.
Recording test results
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any
###################################################################################
############################## FAILED TESTS (if any) ##############################
All tests passed
Success: TEZ-3431 PreCommit Build #2611
Posted by Apache Jenkins Server <je...@builds.apache.org>.
Jira: https://issues.apache.org/jira/browse/TEZ-3431
Build: https://builds.apache.org/job/PreCommit-TEZ-Build/2611/
###################################################################################
########################## LAST 60 LINES OF THE CONSOLE ###########################
[...truncated 339.74 KB...]
[INFO] Tez ................................................ SUCCESS [ 0.023 s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 54:35 min
[INFO] Finished at: 2017-08-13T06:52:49Z
[INFO] Final Memory: 89M/1428M
[INFO] ------------------------------------------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12881642/TEZ-3431.patch
against master revision 1061cf5.
{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 findbugs{color}. The patch does not introduce any new Findbugs (version 3.0.1) 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 .
Test results: https://builds.apache.org/job/PreCommit-TEZ-Build/2611//testReport/
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/2611//console
This message is automatically generated.
======================================================================
======================================================================
Adding comment to Jira.
======================================================================
======================================================================
Comment added.
172495c0f14b051b9b68abec30bc1fc48d92e3d2 logged out
======================================================================
======================================================================
Finished build.
======================================================================
======================================================================
Archiving artifacts
[description-setter] Description set: TEZ-3431
Recording test results
Email was triggered for: Success
Sending email for trigger: Success
###################################################################################
############################## FAILED TESTS (if any) ##############################
All tests passed
Failed: TEZ-3816 PreCommit Build #2610
Posted by Apache Jenkins Server <je...@builds.apache.org>.
Jira: https://issues.apache.org/jira/browse/TEZ-3816
Build: https://builds.apache.org/job/PreCommit-TEZ-Build/2610/
###################################################################################
########################## LAST 60 LINES OF THE CONSOLE ###########################
[...truncated 339.87 KB...]
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 55:47 min
[INFO] Finished at: 2017-08-10T22:24:05Z
[INFO] Final Memory: 89M/1431M
[INFO] ------------------------------------------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12881087/TEZ-3816.001.patch
against master revision 1061cf5.
{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 findbugs{color}. The patch does not introduce any new Findbugs (version 3.0.1) 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 .
Test results: https://builds.apache.org/job/PreCommit-TEZ-Build/2610//testReport/
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/2610//console
This message is automatically generated.
======================================================================
======================================================================
Adding comment to Jira.
======================================================================
======================================================================
Comment added.
fad6b0102385c0a152d619fbd7cda1baee4f1ada 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 - Any
Sending email for trigger: Failure - Any
###################################################################################
############################## FAILED TESTS (if any) ##############################
All tests passed
Failed: TEZ-3813 PreCommit Build #2609
Posted by Apache Jenkins Server <je...@builds.apache.org>.
Jira: https://issues.apache.org/jira/browse/TEZ-3813
Build: https://builds.apache.org/job/PreCommit-TEZ-Build/2609/
###################################################################################
########################## LAST 60 LINES OF THE CONSOLE ###########################
[...truncated 332.86 KB...]
[ERROR] [Help 2] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn <goals> -rf :tez-dag
[INFO] Build failures were ignored.
{color:red}-1 overall{color}. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12881081/TEZ-3813.006.patch
against master revision 8dcf8a1.
{color:green}+1 @author{color}. The patch does not contain any @author tags.
{color:green}+1 tests included{color}. The patch appears to include 3 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 findbugs{color}. The patch does not introduce any new Findbugs (version 3.0.1) 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 :
org.apache.tez.dag.app.rm.TestTaskScheduler
Test results: https://builds.apache.org/job/PreCommit-TEZ-Build/2609//testReport/
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/2609//console
This message is automatically generated.
======================================================================
======================================================================
Adding comment to Jira.
======================================================================
======================================================================
Comment added.
42b5e6e2ad42bf31f322cbba6af94f928cd8b407 logged out
======================================================================
======================================================================
Finished build.
======================================================================
======================================================================
Build step 'Execute shell' marked build as failure
Archiving artifacts
[Fast Archiver] Compressed 3.50 MB of artifacts by 13.4% relative to #2605
[description-setter] Could not determine description.
Recording test results
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any
###################################################################################
############################## FAILED TESTS (if any) ##############################
1 tests failed.
FAILED: org.apache.tez.dag.app.rm.TestTaskScheduler.testTaskSchedulerDetermineMinHeldContainers
Error Message:
AppFinalStatus cannot be returned by isSession()
isSession() should return boolean
***
If you're unsure why you're getting above error read on.
Due to the nature of the syntax above problem might occur because:
1. This exception *might* occur in wrongly written multi-threaded tests.
Please refer to Mockito FAQ on limitations of concurrency testing.
2. A spy is stubbed using when(spy.foo()).then() syntax. It is safer to stub spies -
- with doReturn|Throw() family of methods. More in javadocs for Mockito.spy() method.
Stack Trace:
org.mockito.exceptions.misusing.WrongTypeOfReturnValue:
AppFinalStatus cannot be returned by isSession()
isSession() should return boolean
***
If you're unsure why you're getting above error read on.
Due to the nature of the syntax above problem might occur because:
1. This exception *might* occur in wrongly written multi-threaded tests.
Please refer to Mockito FAQ on limitations of concurrency testing.
2. A spy is stubbed using when(spy.foo()).then() syntax. It is safer to stub spies -
- with doReturn|Throw() family of methods. More in javadocs for Mockito.spy() method.
at org.apache.tez.dag.app.rm.TestTaskScheduler.testTaskSchedulerDetermineMinHeldContainers(TestTaskScheduler.java:965)