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/04/09 03:27:26 UTC

Failed: TEZ-3044 PreCommit Build #1642

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

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

======================================================================
======================================================================
    Testing patch for TEZ-3044.
======================================================================
======================================================================


HEAD is now at 53981d4 TEZ-3208. Update version to 0.8.4-SNAPSHOT, and add section to
Previous HEAD position was 53981d4... TEZ-3208. Update version to 0.8.4-SNAPSHOT, and add section to CHANGES.txt in prepartion for 0.8.3 release.
Switched to branch 'master'
Your branch is behind 'origin/master' by 5 commits, 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 53981d4d277f0a1cd9a8a4aa04a1a6ea01dce6cf.
TEZ-3044 patch is being downloaded at Sat Apr  9 01:27:28 UTC 2016 from
http://issues.apache.org/jira/secure/attachment/12782593/TEZ-3044.1.wip.txt
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/12782593/TEZ-3044.1.wip.txt
  against master revision 53981d4.

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

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

This message is automatically generated.


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


Comment added.
97bacf81f47b8a1a3e8b10ccfdd3d5ea817f0cbf 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-1869 PreCommit Build #1645

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

###################################################################################
########################## LAST 60 LINES OF THE CONSOLE ###########################
[...truncated 4662 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/12688151/TEZ-1869.1.txt
  against master revision 53981d4.

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

This message is automatically generated.


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


Comment added.
a43150c4e9ec427f8a0706586815af7d60a5bf8f 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_000004_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:1272)

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: 1249663113
);
-> 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.setApplicationRegistrationData(
    0,
    Mock for Resource, hashCode: 697872531,
    Mock for Map, hashCode: 1735432250,
    null
);
-> at org.apache.tez.dag.app.rm.TaskSchedulerContextImpl.setApplicationRegistrationData(TaskSchedulerContextImpl.java:96)

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

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)

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

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



Stack Trace:
org.mockito.exceptions.verification.WantedButNotInvoked: 
Wanted but not invoked:
taskSchedulerManagerForTest.taskAllocated(
    0,
    Mock for TA attempt_0_0001_0_01_000004_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:1272)

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: 1249663113
);
-> 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.setApplicationRegistrationData(
    0,
    Mock for Resource, hashCode: 697872531,
    Mock for Map, hashCode: 1735432250,
    null
);
-> at org.apache.tez.dag.app.rm.TaskSchedulerContextImpl.setApplicationRegistrationData(TaskSchedulerContextImpl.java:96)

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

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)

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

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


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

Failed: TEZ-1019 PreCommit Build #1644

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

###################################################################################
########################## LAST 60 LINES OF THE CONSOLE ###########################
[...truncated 21 lines...]
[PreCommit-TEZ-Build] $ /bin/bash /tmp/hudson3506735274401944098.sh
Running in Jenkins mode


======================================================================
======================================================================
    Testing patch for TEZ-1019.
======================================================================
======================================================================


HEAD is now at 53981d4 TEZ-3208. Update version to 0.8.4-SNAPSHOT, and add section to
Switched to branch 'master'
Your branch is up-to-date with 'origin/master'.
Current branch master is up to date.
TEZ-1019 patch is being downloaded at Sat Apr  9 01:27:43 UTC 2016 from
http://issues.apache.org/jira/secure/attachment/12697692/TEZ-1019-5.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/12697692/TEZ-1019-5.patch
  against master revision 53981d4.

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

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

This message is automatically generated.


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


Comment added.
92032b445ae7b956c3c37d6322cdb3608858fd92 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-391 PreCommit Build #1643

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

###################################################################################
########################## LAST 60 LINES OF THE CONSOLE ###########################
[...truncated 21 lines...]
[PreCommit-TEZ-Build] $ /bin/bash /tmp/hudson5315307709388833829.sh
Running in Jenkins mode


======================================================================
======================================================================
    Testing patch for TEZ-391.
======================================================================
======================================================================


HEAD is now at 53981d4 TEZ-3208. Update version to 0.8.4-SNAPSHOT, and add section to
Switched to branch 'master'
Your branch is up-to-date with 'origin/master'.
Current branch master is up to date.
TEZ-391 patch is being downloaded at Sat Apr  9 01:27:36 UTC 2016 from
http://issues.apache.org/jira/secure/attachment/12734397/TEZ-391-WIP-7.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/12734397/TEZ-391-WIP-7.patch
  against master revision 53981d4.

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

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

This message is automatically generated.


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


Comment added.
6be0eac8631c80b1a1190f2a155ca185579532bd 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.