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 2016/06/24 23:27:36 UTC

Failed: TEZ-3311 PreCommit Build #1812

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

###################################################################################
########################## LAST 60 LINES OF THE CONSOLE ###########################
[...truncated 4106 lines...]
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 58:30 min
[INFO] Finished at: 2016-06-24T23:27:33+00:00
[INFO] Final Memory: 73M/1203M
[INFO] ------------------------------------------------------------------------




{color:red}-1 overall{color}.  Here are the results of testing the latest attachment
  http://issues.apache.org/jira/secure/attachment/12813137/TEZ-3311.001.patch
  against master revision 1264d5d.

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

This message is automatically generated.


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


Comment added.
4d8b73d0fd17535c5c4bb55508c02f407653d4c8 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

Success: TEZ-3308 PreCommit Build #1816

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

###################################################################################
########################## LAST 60 LINES OF THE CONSOLE ###########################
[...truncated 4131 lines...]
[INFO] Tez ............................................... SUCCESS [  0.025 s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 59:09 min
[INFO] Finished at: 2016-06-28T01:07:02+00:00
[INFO] Final Memory: 72M/843M
[INFO] ------------------------------------------------------------------------




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

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

This message is automatically generated.


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


Comment added.
9b9cd1383fee041ea2a685a73b0480092380983b logged out


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


Archiving artifacts
[description-setter] Description set: TEZ-3308
Recording test results
Email was triggered for: Success
Sending email for trigger: Success



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

Failed: TEZ-3302 PreCommit Build #1815

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

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

======================================================================
======================================================================
    Testing patch for TEZ-3302.
======================================================================
======================================================================


HEAD is now at d2b9222 TEZ-3302. Add a version of processorContext.waitForAllInputsReady and
Previous HEAD position was d2b9222... TEZ-3302. Add a version of processorContext.waitForAllInputsReady and waitForAnyInputReady with a timeout. Contributed by Tsuyoshi Ozawa.
Switched to branch 'master'
Your branch is behind 'origin/master' by 1 commit, and can be fast-forwarded.
  (use "git pull" to update your local branch)
First, rewinding head to replay your work on top of it...
Fast-forwarded master to d2b9222fb589ce85124b1e381ba199621e91b263.
TEZ-3302 patch is being downloaded at Mon Jun 27 19:58:45 UTC 2016 from
http://issues.apache.org/jira/secure/attachment/12813822/TEZ-3302.002.withLongerTestTimeout.patch
The patch does not appear to apply with p0 to p2
PATCH APPLICATION FAILED




{color:red}-1 overall{color}.  Here are the results of testing the latest attachment
  http://issues.apache.org/jira/secure/attachment/12813822/TEZ-3302.002.withLongerTestTimeout.patch
  against master revision d2b9222.

    {color:red}-1 patch{color}.  The patch command could not apply the patch.

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

This message is automatically generated.


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


Comment added.
92393d9d5229958711e5511163ce66b1f295875a logged out


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


Build step 'Execute shell' marked build as failure
Archiving artifacts
[description-setter] Could not determine description.
Recording test results
ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any



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

Failed: TEZ-2608 PreCommit Build #1814

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

###################################################################################
########################## LAST 60 LINES OF THE CONSOLE ###########################
[...truncated 4104 lines...]
[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/12813813/TEZ-2608.002.patch
  against master revision 2c22e23.

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

This message is automatically generated.


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


Comment added.
fe06f1443ee0357747548177b035841677adcb12 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) ##############################
1 tests failed.
FAILED:  org.apache.tez.dag.app.rm.TestContainerReuse.testReuseConflictLocalResources

Error Message:

Wanted but not invoked:
taskSchedulerManagerForTest.taskAllocated(
    0,
    Mock for TA attempt_0_0001_0_01_000003_1,
    <any>,
    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.TestContainerReuse.testReuseConflictLocalResources(TestContainerReuse.java:1254)

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.testReuseConflictLocalResources(TestContainerReuse.java:1143)

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

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

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

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

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

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

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

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

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

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

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

taskSchedulerManagerForTest.taskAllocated(
    0,
    Mock for TA attempt_0_0001_0_01_000001_1,
    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:69)

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

taskSchedulerManagerForTest.taskAllocated(
    0,
    Mock for TA attempt_0_0001_0_01_000002_1,
    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:69)

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

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



Stack Trace:
org.mockito.exceptions.verification.WantedButNotInvoked: 
Wanted but not invoked:
taskSchedulerManagerForTest.taskAllocated(
    0,
    Mock for TA attempt_0_0001_0_01_000003_1,
    <any>,
    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.TestContainerReuse.testReuseConflictLocalResources(TestContainerReuse.java:1254)

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.testReuseConflictLocalResources(TestContainerReuse.java:1143)

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

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

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

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

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

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

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

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

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

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

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

taskSchedulerManagerForTest.taskAllocated(
    0,
    Mock for TA attempt_0_0001_0_01_000001_1,
    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:69)

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

taskSchedulerManagerForTest.taskAllocated(
    0,
    Mock for TA attempt_0_0001_0_01_000002_1,
    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:69)

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

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


	at org.apache.tez.dag.app.rm.TestContainerReuse.testReuseConflictLocalResources(TestContainerReuse.java:1254)



Failed: TEZ-3287 PreCommit Build #1813

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

###################################################################################
########################## LAST 60 LINES OF THE CONSOLE ###########################
[...truncated 4104 lines...]
[INFO] Total time: 54:41 min
[INFO] Finished at: 2016-06-25T00:43:16+00:00
[INFO] Final Memory: 80M/961M
[INFO] ------------------------------------------------------------------------




{color:red}-1 overall{color}.  Here are the results of testing the latest attachment
  http://issues.apache.org/jira/secure/attachment/12813151/TEZ-3287.001.patch
  against master revision 1264d5d.

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

This message is automatically generated.


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


Comment added.
e52c6437b1b05078c013e272c27e97ad897f1565 logged out


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


Build step 'Execute shell' marked build as failure
Archiving artifacts
Compressed 3.20 MB of artifacts by 27.4% relative to #1811
[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