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

TezQA commented on TEZ-3629:
----------------------------

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

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

    {color:green}+1 tests included{color}.  The patch appears to include 3 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:red}-1 core tests{color}.  The following test timeouts occurred in :
 org.apache.tez.test.TestFaultTolerance

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

This message is automatically generated.

> Tez UI: Enable the UI to display log links from LLAP
> ----------------------------------------------------
>
>                 Key: TEZ-3629
>                 URL: https://issues.apache.org/jira/browse/TEZ-3629
>             Project: Apache Tez
>          Issue Type: Bug
>            Reporter: Sreenath Somarajapuram
>            Assignee: Sreenath Somarajapuram
>         Attachments: TEZ-3629.1.patch
>
>
> LLAP generates one log file per node per query. Once a query completes, LLAP 
> appends a ".done" suffix to the query log file, so that it can be aggregated 
> by YARN.
> On the UI, for LLAP jobs, we need to show links based on the status of the 
> DAG.



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

Reply via email to