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

TezQA commented on TEZ-2259:
----------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment
  http://issues.apache.org/jira/secure/attachment/12724654/TEZ-2259.3.patch
  against master revision c8ef244.

    {color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

    {color:green}+1 tests included{color}.  The patch appears to include 5 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 2.0.3) warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

    {color:red}-1 core tests{color}.  The following test timeouts occurred in :
 org.apache.tez.test.TestSecureShuffle
org.apache.tez.test.TestFaultTolerance

Test results: https://builds.apache.org/job/PreCommit-TEZ-Build/442//testReport/
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/442//console

This message is automatically generated.

> Push additional data to Timeline for Recovery for better consumption in UI
> --------------------------------------------------------------------------
>
>                 Key: TEZ-2259
>                 URL: https://issues.apache.org/jira/browse/TEZ-2259
>             Project: Apache Tez
>          Issue Type: Bug
>            Reporter: Hitesh Shah
>            Assignee: Hitesh Shah
>         Attachments: TEZ-2259.1.patch, TEZ-2259.2.patch, TEZ-2259.3.patch
>
>
> Some things I can think of: 
>  
>    - applicationAttemptId in which the dag was submitted
>    - appAttemptId in which the dag was completed 
> Above provides implicit information on how many app attempts the dag spanned 
> ( and therefore recovered how many times ).
>   
>    - Maybe an implicit event mentioning that the DAG was recovered and in 
> which attempt it was recovered. Possibly add information on what state was 
> recovered?



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

Reply via email to