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

TezQA commented on TEZ-2990:
----------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment
  http://issues.apache.org/jira/secure/attachment/12776992/TEZ-2990.1.txt
  against master revision b03faf1.

    {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:red}-1 release audit{color}.  The applied patch generated 1 
release audit warnings.

    {color:red}-1 core tests{color}.  The patch failed these unit tests in :
                   org.apache.tez.dag.app.dag.impl.TestVertexImpl

Test results: 
https://builds.apache.org/job/PreCommit-TEZ-Build/1360//testReport/
Release audit warnings: 
https://builds.apache.org/job/PreCommit-TEZ-Build/1360//artifact/patchprocess/patchReleaseAuditProblems.txt
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/1360//console

This message is automatically generated.

> test-patch bails out early if tests fails
> -----------------------------------------
>
>                 Key: TEZ-2990
>                 URL: https://issues.apache.org/jira/browse/TEZ-2990
>             Project: Apache Tez
>          Issue Type: Bug
>            Reporter: Siddharth Seth
>            Assignee: Siddharth Seth
>         Attachments: TEZ-2990.1.txt
>
>
> test-patch is making use of -fae -> which does not run tests on downstream 
> modules if tests in an upstream module failed.
> Instead, we should be running -fn



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to