Jira: https://issues.apache.org/jira/browse/TEZ-3632
Build: https://builds.apache.org/job/PreCommit-TEZ-Build/2308/
###################################################################################
########################## LAST 60 LINES OF THE CONSOLE
###########################
[...truncated 1.51 KB...]
======================================================================
======================================================================
Testing patch for TEZ-3632.
======================================================================
======================================================================
HEAD is now at d40f3ad TEZ-3503. Tez UI: Support search by queue name (sree)
Previous HEAD position was d40f3ad... TEZ-3503. Tez UI: Support search by queue
name (sree)
Switched to branch 'master'
Your branch is behind 'origin/master' by 25 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 d40f3ad719e6713d4b1dbf1dc1e9646f79f21c3d.
TEZ-3632 patch is being downloaded at Tue Mar 7 16:09:20 UTC 2017 from
http://issues.apache.org/jira/secure/attachment/12853784/TEZ-3632-branch-0.7.001.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/12853784/TEZ-3632-branch-0.7.001.patch
against master revision d40f3ad.
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/2308//console
This message is automatically generated.
======================================================================
======================================================================
Adding comment to Jira.
======================================================================
======================================================================
Comment added.
43c5041073fc348449083417fbe19b6e3ed3fb0b 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.