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

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

  Running tests 
  /home/jenkins/tools/maven/latest/bin/mvn clean install -fn -DTezPatchProcess
cat: 
/home/jenkins/jenkins-slave/workspace/PreCommit-TEZ-Build/../patchprocess/testrun.txt:
 No such file or directory
awk: cannot open 
/home/jenkins/jenkins-slave/workspace/PreCommit-TEZ-Build/../patchprocess/testrun.txt
 (No such file or directory)




{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment
  http://issues.apache.org/jira/secure/attachment/12708304/TEZ-1909-4.patch
  against master revision 008f9bc.

    {color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

    {color:green}+1 tests included{color}.  The patch appears to include 3 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 2.0.3) 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/369//testReport/
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/369//console

This message is automatically generated.


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


Comment added.
47381aad5c03d14c1cc6e47540cba9667426834b logged out


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


Archiving artifacts
ERROR: No artifacts found that match the file pattern "patchprocess/*.*". 
Configuration error?
ERROR: ?patchprocess/*.*? doesn?t match anything, but ?*.*? does. Perhaps 
that?s what you mean?
Build step 'Archive the artifacts' changed build result to FAILURE
[description-setter] Could not determine description.
Recording test results
Email was triggered for: Failure
Sending email for trigger: Failure



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

Reply via email to