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 2015/09/09 22:59:22 UTC

Failed: TEZ-2787 PreCommit Build #1100

Jira: https://issues.apache.org/jira/browse/TEZ-2787
Build: https://builds.apache.org/job/PreCommit-TEZ-Build/1100/

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



{color:red}-1 overall{color}.  Here are the results of testing the latest attachment
  http://issues.apache.org/jira/secure/attachment/12754982/TEZ-2787.1.patch
  against master revision 00508f8.

    {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/1100//testReport/
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/1100//console

This message is automatically generated.


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


Comment added.
e864a7425c72b479e2a8218213fde684c7a5d88d logged out


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


Build step 'Execute shell' marked build as failure
Archiving artifacts
Sending artifact delta relative to PreCommit-TEZ-Build #1098
Archived 53 artifacts
Archive block size is 32768
Received 26 blocks and 2396474 bytes
Compression is 26.2%
Took 0.59 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

Success: TEZ-2792 PreCommit Build #1103

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

###################################################################################
########################## LAST 60 LINES OF THE CONSOLE ###########################
[...truncated 3451 lines...]
[INFO] Final Memory: 87M/1096M
[INFO] ------------------------------------------------------------------------




{color:green}+1 overall{color}.  Here are the results of testing the latest attachment
  http://issues.apache.org/jira/secure/attachment/12755096/TEZ-2792.2.patch
  against master revision 00508f8.

    {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/1103//testReport/
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/1103//console

This message is automatically generated.


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


Comment added.
a4c11f92b323e014923932b2e125fda0bdc828c2 logged out


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


Archiving artifacts
Sending artifact delta relative to PreCommit-TEZ-Build #1098
Archived 53 artifacts
Archive block size is 32768
Received 8 blocks and 2988463 bytes
Compression is 8.1%
Took 1.4 sec
Description set: TEZ-2792
Recording test results
Email was triggered for: Success
Sending email for trigger: Success



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

Failed: TEZ-2164 PreCommit Build #1102

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

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


======================================================================
======================================================================
    Determining number of patched javac warnings.
======================================================================
======================================================================


/home/jenkins/tools/maven/latest/bin/mvn clean test -DskipTests -Ptest-patch > /home/jenkins/jenkins-slave/workspace/PreCommit-TEZ-Build/../patchprocess/patchJavacWarnings.txt 2>&1




{color:red}-1 overall{color}.  Here are the results of testing the latest attachment
  http://issues.apache.org/jira/secure/attachment/12755022/TEZ-2164.4.patch
  against master revision 00508f8.

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:green}+1 tests included{color}.  The patch appears to include 89 new or modified test files.

    {color:red}-1 javac{color:red}.  The patch appears to cause the build to fail.

Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/1102//console

This message is automatically generated.


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


Comment added.
49c99240e63e14332a446250f880ae9a66720e06 logged out


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


Build step 'Execute shell' marked build as failure
Archiving artifacts
Sending artifact delta relative to PreCommit-TEZ-Build #1098
Archived 3 artifacts
Archive block size is 32768
Received 0 blocks and 831007 bytes
Compression is 0.0%
Took 0.27 sec
[description-setter] Could not determine description.
Recording test results
Email was triggered for: Failure
Sending email for trigger: Failure



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

Failed: TEZ-2774 PreCommit Build #1101

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

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


{color:red}-1 overall{color}.  Here are the results of testing the latest attachment
  http://issues.apache.org/jira/secure/attachment/12755020/TEZ-2774.3.txt
  against master revision 00508f8.

    {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.TestContainerReuse

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

This message is automatically generated.


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


Comment added.
bf7c2964aaf1e2e065ba1d2cef915f344fa4cd70 logged out


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


Build step 'Execute shell' marked build as failure
Archiving artifacts
Sending artifact delta relative to PreCommit-TEZ-Build #1098
Archived 53 artifacts
Archive block size is 32768
Received 4 blocks and 3117867 bytes
Compression is 4.0%
Took 0.66 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.TestContainerReuse.testReuseWithTaskSpecificLaunchCmdOption

Error Message:

Wanted but not invoked:
taskSchedulerManagerForTest.taskAllocated(
    0,
    Mock for TaskAttempt, hashCode: 997690982,
    <any>,
    Container: [ContainerId: container_1_0001_01_000002, NodeId: host3:0, NodeHttpAddress: host3:0, Resource: <memory:1024, vCores:1>, Priority: 1, Token: null, ]
);
-> at org.apache.tez.dag.app.rm.TestContainerReuse.testReuseWithTaskSpecificLaunchCmdOption(TestContainerReuse.java:686)

However, there were other interactions with this mock:
taskSchedulerManagerForTest.init(
    Configuration: core-default.xml, core-site.xml, yarn-default.xml, yarn-site.xml
);
-> at org.apache.tez.dag.app.rm.TestContainerReuse.testReuseWithTaskSpecificLaunchCmdOption(TestContainerReuse.java:537)

taskSchedulerManagerForTest.setConfig(
    Configuration: core-default.xml, core-site.xml, yarn-default.xml, yarn-site.xml
);
-> at org.apache.tez.dag.app.rm.TestContainerReuse.testReuseWithTaskSpecificLaunchCmdOption(TestContainerReuse.java:537)

taskSchedulerManagerForTest.serviceInit(
    Configuration: core-default.xml, core-site.xml, yarn-default.xml, yarn-site.xml
);
-> at org.apache.tez.dag.app.rm.TestContainerReuse.testReuseWithTaskSpecificLaunchCmdOption(TestContainerReuse.java:537)

taskSchedulerManagerForTest.start();
-> at org.apache.tez.dag.app.rm.TestContainerReuse.testReuseWithTaskSpecificLaunchCmdOption(TestContainerReuse.java:538)

taskSchedulerManagerForTest.serviceStart();
-> at org.apache.tez.dag.app.rm.TestContainerReuse.testReuseWithTaskSpecificLaunchCmdOption(TestContainerReuse.java:538)

taskSchedulerManagerForTest.instantiateSchedulers(
    "host",
    0,
    "",
    Mock for AppContext, hashCode: 1483250420
);
-> at org.apache.tez.dag.app.rm.TestContainerReuse.testReuseWithTaskSpecificLaunchCmdOption(TestContainerReuse.java:538)

taskSchedulerManagerForTest.getContainerSignatureMatcher();
-> at org.apache.tez.dag.app.rm.TestContainerReuse.testReuseWithTaskSpecificLaunchCmdOption(TestContainerReuse.java:538)

taskSchedulerManagerForTest.getConfig();
-> at org.apache.tez.dag.app.rm.TestContainerReuse.testReuseWithTaskSpecificLaunchCmdOption(TestContainerReuse.java:538)

taskSchedulerManagerForTest.setApplicationRegistrationData(
    0,
    Mock for Resource, hashCode: 999634564,
    Mock for Map, hashCode: 1093546667,
    null
);
-> at org.apache.tez.dag.app.rm.TaskSchedulerContextImpl.setApplicationRegistrationData(TaskSchedulerContextImpl.java:92)

taskSchedulerManagerForTest.getSpyTaskScheduler();
-> at org.apache.tez.dag.app.rm.TestContainerReuse.testReuseWithTaskSpecificLaunchCmdOption(TestContainerReuse.java:540)

taskSchedulerManagerForTest.handleEvent(
    EventType: S_TA_LAUNCH_REQUEST
);
-> at org.apache.tez.dag.app.rm.TestContainerReuse.testReuseWithTaskSpecificLaunchCmdOption(TestContainerReuse.java:577)

taskSchedulerManagerForTest.handleEvent(
    EventType: S_TA_LAUNCH_REQUEST
);
-> at org.apache.tez.dag.app.rm.TestContainerReuse.testReuseWithTaskSpecificLaunchCmdOption(TestContainerReuse.java:580)

taskSchedulerManagerForTest.taskAllocated(
    0,
    Mock for TaskAttempt, hashCode: 1205087790,
    EventType: S_TA_LAUNCH_REQUEST,
    Container: [ContainerId: container_1_0001_01_000001, NodeId: host1:0, NodeHttpAddress: host1:0, Resource: <memory:1024, vCores:1>, Priority: 1, Token: null, ]
);
-> at org.apache.tez.dag.app.rm.TaskSchedulerContextImpl.taskAllocated(TaskSchedulerContextImpl.java:65)

taskSchedulerManagerForTest.handleEvent(
    EventType: S_TA_ENDED
);
-> at org.apache.tez.dag.app.rm.TestContainerReuse.testReuseWithTaskSpecificLaunchCmdOption(TestContainerReuse.java:594)

taskSchedulerManagerForTest.containerBeingReleased(
    0,
    container_1_0001_01_000001
);
-> at org.apache.tez.dag.app.rm.TaskSchedulerContextImpl.containerBeingReleased(TaskSchedulerContextImpl.java:75)

taskSchedulerManagerForTest.handleEvent(
    EventType: S_TA_LAUNCH_REQUEST
);
-> at org.apache.tez.dag.app.rm.TestContainerReuse.testReuseWithTaskSpecificLaunchCmdOption(TestContainerReuse.java:627)

taskSchedulerManagerForTest.handleEvent(
    EventType: S_TA_LAUNCH_REQUEST
);
-> at org.apache.tez.dag.app.rm.TestContainerReuse.testReuseWithTaskSpecificLaunchCmdOption(TestContainerReuse.java:630)

taskSchedulerManagerForTest.taskAllocated(
    0,
    Mock for TaskAttempt, hashCode: 1852930389,
    EventType: S_TA_LAUNCH_REQUEST,
    Container: [ContainerId: container_1_0001_01_000002, NodeId: host2:0, NodeHttpAddress: host2:0, Resource: <memory:1024, vCores:1>, Priority: 1, Token: null, ]
);
-> at org.apache.tez.dag.app.rm.TaskSchedulerContextImpl.taskAllocated(TaskSchedulerContextImpl.java:65)

taskSchedulerManagerForTest.handleEvent(
    EventType: S_TA_ENDED
);
-> at org.apache.tez.dag.app.rm.TestContainerReuse.testReuseWithTaskSpecificLaunchCmdOption(TestContainerReuse.java:642)

taskSchedulerManagerForTest.containerBeingReleased(
    0,
    container_1_0001_01_000002
);
-> at org.apache.tez.dag.app.rm.TaskSchedulerContextImpl.containerBeingReleased(TaskSchedulerContextImpl.java:75)

taskSchedulerManagerForTest.handleEvent(
    EventType: S_TA_LAUNCH_REQUEST
);
-> at org.apache.tez.dag.app.rm.TestContainerReuse.testReuseWithTaskSpecificLaunchCmdOption(TestContainerReuse.java:679)

taskSchedulerManagerForTest.handleEvent(
    EventType: S_TA_LAUNCH_REQUEST
);
-> at org.apache.tez.dag.app.rm.TestContainerReuse.testReuseWithTaskSpecificLaunchCmdOption(TestContainerReuse.java:680)



Stack Trace:
org.mockito.exceptions.verification.WantedButNotInvoked: 
Wanted but not invoked:
taskSchedulerManagerForTest.taskAllocated(
    0,
    Mock for TaskAttempt, hashCode: 997690982,
    <any>,
    Container: [ContainerId: container_1_0001_01_000002, NodeId: host3:0, NodeHttpAddress: host3:0, Resource: <memory:1024, vCores:1>, Priority: 1, Token: null, ]
);
-> at org.apache.tez.dag.app.rm.TestContainerReuse.testReuseWithTaskSpecificLaunchCmdOption(TestContainerReuse.java:686)

However, there were other interactions with this mock:
taskSchedulerManagerForTest.init(
    Configuration: core-default.xml, core-site.xml, yarn-default.xml, yarn-site.xml
);
-> at org.apache.tez.dag.app.rm.TestContainerReuse.testReuseWithTaskSpecificLaunchCmdOption(TestContainerReuse.java:537)

taskSchedulerManagerForTest.setConfig(
    Configuration: core-default.xml, core-site.xml, yarn-default.xml, yarn-site.xml
);
-> at org.apache.tez.dag.app.rm.TestContainerReuse.testReuseWithTaskSpecificLaunchCmdOption(TestContainerReuse.java:537)

taskSchedulerManagerForTest.serviceInit(
    Configuration: core-default.xml, core-site.xml, yarn-default.xml, yarn-site.xml
);
-> at org.apache.tez.dag.app.rm.TestContainerReuse.testReuseWithTaskSpecificLaunchCmdOption(TestContainerReuse.java:537)

taskSchedulerManagerForTest.start();
-> at org.apache.tez.dag.app.rm.TestContainerReuse.testReuseWithTaskSpecificLaunchCmdOption(TestContainerReuse.java:538)

taskSchedulerManagerForTest.serviceStart();
-> at org.apache.tez.dag.app.rm.TestContainerReuse.testReuseWithTaskSpecificLaunchCmdOption(TestContainerReuse.java:538)

taskSchedulerManagerForTest.instantiateSchedulers(
    "host",
    0,
    "",
    Mock for AppContext, hashCode: 1483250420
);
-> at org.apache.tez.dag.app.rm.TestContainerReuse.testReuseWithTaskSpecificLaunchCmdOption(TestContainerReuse.java:538)

taskSchedulerManagerForTest.getContainerSignatureMatcher();
-> at org.apache.tez.dag.app.rm.TestContainerReuse.testReuseWithTaskSpecificLaunchCmdOption(TestContainerReuse.java:538)

taskSchedulerManagerForTest.getConfig();
-> at org.apache.tez.dag.app.rm.TestContainerReuse.testReuseWithTaskSpecificLaunchCmdOption(TestContainerReuse.java:538)

taskSchedulerManagerForTest.setApplicationRegistrationData(
    0,
    Mock for Resource, hashCode: 999634564,
    Mock for Map, hashCode: 1093546667,
    null
);
-> at org.apache.tez.dag.app.rm.TaskSchedulerContextImpl.setApplicationRegistrationData(TaskSchedulerContextImpl.java:92)

taskSchedulerManagerForTest.getSpyTaskScheduler();
-> at org.apache.tez.dag.app.rm.TestContainerReuse.testReuseWithTaskSpecificLaunchCmdOption(TestContainerReuse.java:540)

taskSchedulerManagerForTest.handleEvent(
    EventType: S_TA_LAUNCH_REQUEST
);
-> at org.apache.tez.dag.app.rm.TestContainerReuse.testReuseWithTaskSpecificLaunchCmdOption(TestContainerReuse.java:577)

taskSchedulerManagerForTest.handleEvent(
    EventType: S_TA_LAUNCH_REQUEST
);
-> at org.apache.tez.dag.app.rm.TestContainerReuse.testReuseWithTaskSpecificLaunchCmdOption(TestContainerReuse.java:580)

taskSchedulerManagerForTest.taskAllocated(
    0,
    Mock for TaskAttempt, hashCode: 1205087790,
    EventType: S_TA_LAUNCH_REQUEST,
    Container: [ContainerId: container_1_0001_01_000001, NodeId: host1:0, NodeHttpAddress: host1:0, Resource: <memory:1024, vCores:1>, Priority: 1, Token: null, ]
);
-> at org.apache.tez.dag.app.rm.TaskSchedulerContextImpl.taskAllocated(TaskSchedulerContextImpl.java:65)

taskSchedulerManagerForTest.handleEvent(
    EventType: S_TA_ENDED
);
-> at org.apache.tez.dag.app.rm.TestContainerReuse.testReuseWithTaskSpecificLaunchCmdOption(TestContainerReuse.java:594)

taskSchedulerManagerForTest.containerBeingReleased(
    0,
    container_1_0001_01_000001
);
-> at org.apache.tez.dag.app.rm.TaskSchedulerContextImpl.containerBeingReleased(TaskSchedulerContextImpl.java:75)

taskSchedulerManagerForTest.handleEvent(
    EventType: S_TA_LAUNCH_REQUEST
);
-> at org.apache.tez.dag.app.rm.TestContainerReuse.testReuseWithTaskSpecificLaunchCmdOption(TestContainerReuse.java:627)

taskSchedulerManagerForTest.handleEvent(
    EventType: S_TA_LAUNCH_REQUEST
);
-> at org.apache.tez.dag.app.rm.TestContainerReuse.testReuseWithTaskSpecificLaunchCmdOption(TestContainerReuse.java:630)

taskSchedulerManagerForTest.taskAllocated(
    0,
    Mock for TaskAttempt, hashCode: 1852930389,
    EventType: S_TA_LAUNCH_REQUEST,
    Container: [ContainerId: container_1_0001_01_000002, NodeId: host2:0, NodeHttpAddress: host2:0, Resource: <memory:1024, vCores:1>, Priority: 1, Token: null, ]
);
-> at org.apache.tez.dag.app.rm.TaskSchedulerContextImpl.taskAllocated(TaskSchedulerContextImpl.java:65)

taskSchedulerManagerForTest.handleEvent(
    EventType: S_TA_ENDED
);
-> at org.apache.tez.dag.app.rm.TestContainerReuse.testReuseWithTaskSpecificLaunchCmdOption(TestContainerReuse.java:642)

taskSchedulerManagerForTest.containerBeingReleased(
    0,
    container_1_0001_01_000002
);
-> at org.apache.tez.dag.app.rm.TaskSchedulerContextImpl.containerBeingReleased(TaskSchedulerContextImpl.java:75)

taskSchedulerManagerForTest.handleEvent(
    EventType: S_TA_LAUNCH_REQUEST
);
-> at org.apache.tez.dag.app.rm.TestContainerReuse.testReuseWithTaskSpecificLaunchCmdOption(TestContainerReuse.java:679)

taskSchedulerManagerForTest.handleEvent(
    EventType: S_TA_LAUNCH_REQUEST
);
-> at org.apache.tez.dag.app.rm.TestContainerReuse.testReuseWithTaskSpecificLaunchCmdOption(TestContainerReuse.java:680)


	at org.apache.tez.dag.app.rm.TestContainerReuse.testReuseWithTaskSpecificLaunchCmdOption(TestContainerReuse.java:686)