Jira: https://issues.apache.org/jira/browse/TEZ-2192
Build: https://builds.apache.org/job/PreCommit-TEZ-Build/380/
###################################################################################
########################## LAST 60 LINES OF THE CONSOLE
###########################
[...truncated 2430 lines...]
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12708900/TEZ-2192.3.patch
against master revision 3bfe003.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 2 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:red}-1 findbugs{color}. The patch appears to introduce 1 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: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/380//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-TEZ-Build/380//artifact/patchprocess/newPatchFindbugsWarningstez-dag.html
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/380//console
This message is automatically generated.
======================================================================
======================================================================
Adding comment to Jira.
======================================================================
======================================================================
Comment added.
95c64fdab8054f4c6c45929c99ae39eb0b94f2f8 logged out
======================================================================
======================================================================
Finished build.
======================================================================
======================================================================
Build step 'Execute shell' marked build as failure
Archiving artifacts
Sending artifact delta relative to PreCommit-TEZ-Build #377
Archived 44 artifacts
Archive block size is 32768
Received 0 blocks and 2742144 bytes
Compression is 0.0%
Took 1.2 sec
[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.tez.dag.app.rm.TestTaskScheduler.testTaskSchedulerWithReuse
Error Message:
Wanted but not invoked:
taskSchedulerAppCallback.containerBeingReleased(
container1
);
-> at
org.apache.tez.dag.app.rm.TestTaskScheduler.testTaskSchedulerWithReuse(TestTaskScheduler.java:742)
However, there were other interactions with this mock:
taskSchedulerAppCallback.setApplicationRegistrationData(
Mock for Resource, hashCode: 1423633034,
Mock for Map, hashCode: 1885091211,
null
);
-> at
org.apache.tez.dag.app.rm.TaskSchedulerAppCallbackWrapper$SetApplicationRegistrationDataCallable.call(TaskSchedulerAppCallbackWrapper.java:244)
taskSchedulerAppCallback.taskAllocated(
task1,
Mock for Object, hashCode: 1452504275,
container1
);
-> at
org.apache.tez.dag.app.rm.TaskSchedulerAppCallbackWrapper$TaskAllocatedCallable.call(TaskSchedulerAppCallbackWrapper.java:152)
taskSchedulerAppCallback.taskAllocated(
task2,
Mock for Object, hashCode: 1792734476,
container2
);
-> at
org.apache.tez.dag.app.rm.TaskSchedulerAppCallbackWrapper$TaskAllocatedCallable.call(TaskSchedulerAppCallbackWrapper.java:152)
taskSchedulerAppCallback.taskAllocated(
task3,
Mock for Object, hashCode: 1292770722,
container3
);
-> at
org.apache.tez.dag.app.rm.TaskSchedulerAppCallbackWrapper$TaskAllocatedCallable.call(TaskSchedulerAppCallbackWrapper.java:152)
Stack Trace:
org.mockito.exceptions.verification.WantedButNotInvoked:
Wanted but not invoked:
taskSchedulerAppCallback.containerBeingReleased(
container1
);
-> at
org.apache.tez.dag.app.rm.TestTaskScheduler.testTaskSchedulerWithReuse(TestTaskScheduler.java:742)
However, there were other interactions with this mock:
taskSchedulerAppCallback.setApplicationRegistrationData(
Mock for Resource, hashCode: 1423633034,
Mock for Map, hashCode: 1885091211,
null
);
-> at
org.apache.tez.dag.app.rm.TaskSchedulerAppCallbackWrapper$SetApplicationRegistrationDataCallable.call(TaskSchedulerAppCallbackWrapper.java:244)
taskSchedulerAppCallback.taskAllocated(
task1,
Mock for Object, hashCode: 1452504275,
container1
);
-> at
org.apache.tez.dag.app.rm.TaskSchedulerAppCallbackWrapper$TaskAllocatedCallable.call(TaskSchedulerAppCallbackWrapper.java:152)
taskSchedulerAppCallback.taskAllocated(
task2,
Mock for Object, hashCode: 1792734476,
container2
);
-> at
org.apache.tez.dag.app.rm.TaskSchedulerAppCallbackWrapper$TaskAllocatedCallable.call(TaskSchedulerAppCallbackWrapper.java:152)
taskSchedulerAppCallback.taskAllocated(
task3,
Mock for Object, hashCode: 1292770722,
container3
);
-> at
org.apache.tez.dag.app.rm.TaskSchedulerAppCallbackWrapper$TaskAllocatedCallable.call(TaskSchedulerAppCallbackWrapper.java:152)
at
org.apache.tez.dag.app.rm.TestTaskScheduler.testTaskSchedulerWithReuse(TestTaskScheduler.java:742)
