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

TezQA commented on TEZ-3700:
----------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment
  http://issues.apache.org/jira/secure/attachment/12865298/TEZ-3700.1.patch
  against master revision 247719d.

    {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/2395//testReport/
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/2395//console

This message is automatically generated.

> Consumer attempt should kill itself instead of failing during validation 
> checks with final merge avoidance
> ----------------------------------------------------------------------------------------------------------
>
>                 Key: TEZ-3700
>                 URL: https://issues.apache.org/jira/browse/TEZ-3700
>             Project: Apache Tez
>          Issue Type: Bug
>            Reporter: Rajesh Balamohan
>            Assignee: Rajesh Balamohan
>         Attachments: TEZ-3700.1.patch
>
>
> Currently when if data is received from different attempts with final merge 
> disabled (with/without pipleining), consumer attempt ends up with failure. 
> Instead it should issue kill request so that the job deos not end up with 
> failures.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to