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

###################################################################################
########################## LAST 60 LINES OF THE CONSOLE 
###########################
[...truncated 1.89 KB...]
HEAD is now at a9b8bb5 TEZ-3770. DAG-aware YARN task scheduler (jlowe)
Previous HEAD position was a9b8bb5... TEZ-3770. DAG-aware YARN task scheduler 
(jlowe)
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 a9b8bb5a6840a89844cd75ec86aab2b7457c8028.
TEZ-3892 patch is being downloaded at Tue Jan 30 22:38:24 UTC 2018 from
http://issues.apache.org/jira/secure/attachment/12908443/TEZ-3892.1.patch
patch: **** malformed patch at line 265:  }

patch: **** malformed patch at line 265:  }

patch: **** malformed patch at line 265:  }

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/12908443/TEZ-3892.1.patch
  against master revision a9b8bb5.

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

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

This message is automatically generated.


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


Unable to log in to server: 
https://issues.apache.org/jira/rpc/soap/jirasoapservice-v2 with user: tezqa.
 Cause: (404)404
Unable to log in to server: 
https://issues.apache.org/jira/rpc/soap/jirasoapservice-v2 with user: tezqa.
 Cause: (404)404


======================================================================
======================================================================
    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.

Reply via email to