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

TezQA commented on TEZ-3857:
----------------------------

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

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

This message is automatically generated.

> Tez TaskImpl can throw Invalid state transition for leaf tasks that do Retro 
> Active Transition
> ----------------------------------------------------------------------------------------------
>
>                 Key: TEZ-3857
>                 URL: https://issues.apache.org/jira/browse/TEZ-3857
>             Project: Apache Tez
>          Issue Type: Bug
>            Reporter: Kuhu Shukla
>            Assignee: Kuhu Shukla
>         Attachments: TEZ-3857.001.patch
>
>
> {code}
> Invalid event T_ATTEMPT_FAILED on Task task_1234_5678_1_01_000001
> {code}
> The task had more than one running attempts, while one of them succeeded and 
> the task was marked succeeded, the second failed and caused the Task state 
> machine to enter error state since the task was in a leaf vertex and does the 
> following:
> {code}
> if (task.leafVertex) {
>         LOG.error("Unexpected event for task of leaf vertex " + 
> event.getType() + ", taskId: "
>             + task.getTaskId());
>         task.internalError(event.getType());
>       }
> {code}
> This JIRA tracks fixing this invalid state.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to