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

TezQA commented on TEZ-2282:
----------------------------

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

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

    {color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
                        Please justify why no new tests are needed for this 
patch.
                        Also please list what manual steps were performed to 
verify this patch.

    {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:green}+1 core tests{color}.  The patch passed unit tests in .

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

This message is automatically generated.

> Delimit reused yarn container logs (stderr, stdout, syslog) with task attempt 
> start/stop events
> -----------------------------------------------------------------------------------------------
>
>                 Key: TEZ-2282
>                 URL: https://issues.apache.org/jira/browse/TEZ-2282
>             Project: Apache Tez
>          Issue Type: Bug
>            Reporter: Jonathan Eagles
>            Assignee: Mit Desai
>         Attachments: TEZ-2282.1.patch, TEZ-2282.2.patch, 
> TEZ-2282.master.1.patch
>
>
> This could help with debugging in some cases where logging is task specific. 
> For example GC log is going to stdout, it will be nice to see task attempt 
> start/stop times



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

Reply via email to