You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tez.apache.org by "TezQA (JIRA)" <ji...@apache.org> on 2017/03/09 11:38:37 UTC

[jira] [Commented] (TEZ-3656) Tez UI: Status correction is not working as expected

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

TezQA commented on TEZ-3656:
----------------------------

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

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

This message is automatically generated.

> Tez UI: Status correction is not working as expected
> ----------------------------------------------------
>
>                 Key: TEZ-3656
>                 URL: https://issues.apache.org/jira/browse/TEZ-3656
>             Project: Apache Tez
>          Issue Type: Bug
>            Reporter: Sreenath Somarajapuram
>            Assignee: Sreenath Somarajapuram
>         Attachments: TEZ-3656.1.patch, TEZ-3656.WIP.1.patch
>
>
> If the application is killed abruptly DAG status remains RUNNING. We use a status correction logic to that depends on application status to display a more appropriate status.
> This is not working as expected now.



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