Jira: https://issues.apache.org/jira/browse/TEZ-3754
Build: https://builds.apache.org/job/PreCommit-TEZ-Build/2518/
###################################################################################
########################## LAST 60 LINES OF THE CONSOLE
###########################
[...truncated 336.04 KB...]
[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/12871814/TEZ-3754.1.patch
against master revision 29b45bc.
{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: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/2518//testReport/
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/2518//console
This message is automatically generated.
======================================================================
======================================================================
Adding comment to Jira.
======================================================================
======================================================================
Comment added.
bd5a357ac31dbbcca2aa4005c212abfca405d877 logged out
======================================================================
======================================================================
Finished build.
======================================================================
======================================================================
Build step 'Execute shell' marked build as failure
Archiving artifacts
Compressed 3.50 MB of artifacts by 10.7% relative to #2515
[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)
