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

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

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
|| || || || {color:brown} Prechecks {color} ||
| {color:red}-1{color} | {color:red} maven {color} | {color:red}  0m  5s{color} 
| {color:red} ERROR: maven was not available. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | TEZ-3891 |
| JIRA Patch URL | 
https://issues.apache.org/jira/secure/attachment/12941465/TEZ-3891.001.patch |
| Optional Tests |  dupname  asflicense  javac  javadoc  unit  findbugs  
checkstyle  compile  |
| uname | Linux asf901.gq1.ygridcore.net 4.4.0-134-generic #160~14.04.1-Ubuntu 
SMP Fri Aug 17 11:07:07 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality | 
/home/jenkins/jenkins-slave/workspace/PreCommit-TEZ-Build-Yetus/yetus/precommit/personality/tez.sh
 |
| git revision | master / 64c04f1 |
| Console output | 
https://builds.apache.org/job/PreCommit-TEZ-Build-Yetus/5/console |
| Powered by | Apache Yetus 0.8.0   http://yetus.apache.org |


This message was 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
>
>
> 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