Jira: https://issues.apache.org/jira/browse/TEZ-3507
Build: https://builds.apache.org/job/PreCommit-TEZ-Build/2090/
###################################################################################
########################## LAST 60 LINES OF THE CONSOLE
###########################
[...truncated 24 lines...]
======================================================================
======================================================================
Testing patch for TEZ-3507.
======================================================================
======================================================================
HEAD is now at ad68f73 TEZ-3493. DAG submit timeout cannot be set to a month
(Hitesh Shah via jeagles)
Previous HEAD position was ad68f73... TEZ-3493. DAG submit timeout cannot be
set to a month (Hitesh Shah via jeagles)
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 ad68f73583681f79d825381d3bed8b80867d87e1.
TEZ-3507 patch is being downloaded at Fri Nov 4 14:57:56 UTC 2016 from
http://issues.apache.org/jira/secure/attachment/12836966/TEZ-3507.1.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/12836966/TEZ-3507.1.patch
against master revision ad68f73.
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/2090//console
This message is automatically generated.
======================================================================
======================================================================
Adding comment to Jira.
======================================================================
======================================================================
Comment added.
9f8516ba4c3bc74d1dc90ee589409e8770a075a3 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.
