[ 
https://issues.apache.org/jira/browse/TEZ-3891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16629941#comment-16629941
 ] 

TezQA commented on TEZ-3891:
----------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment
  http://issues.apache.org/jira/secure/attachment/12941487/TEZ-3891.002.patch
  against master revision 64c04f1.

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

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

This message is automatically generated.


> Migrate patch submisssion scripts and hooks to Yetus 0.8.0
> ----------------------------------------------------------
>
>                 Key: TEZ-3891
>                 URL: https://issues.apache.org/jira/browse/TEZ-3891
>             Project: Apache Tez
>          Issue Type: Improvement
>            Reporter: Eric Wohlstadter
>            Assignee: Jonathan Eagles
>            Priority: Major
>         Attachments: TEZ-3891.001.patch, TEZ-3891.002.patch
>
>
> Patch test/validation results are no longer posted to JIRA. This is due to 
> EOL for some APIs that were used being used. 
> Discussed with [~jlowe] and [~jeagles]. 
> As suggested by [~aw], moving to Yetus 0.7.0 seems to the most sense, rather 
> than try to workaround and carry forward the older scripts. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to