TezQA commented on TEZ-3554:

{color:red}-1 overall{color}.  Here are the results of testing the latest 
  against master revision 8079919.

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

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

This message is automatically generated.

> Add a link to get to all logs from Tez UI while job is running
> --------------------------------------------------------------
>                 Key: TEZ-3554
>                 URL: https://issues.apache.org/jira/browse/TEZ-3554
>             Project: Apache Tez
>          Issue Type: Improvement
>            Reporter: Eric Badger
>            Assignee: Eric Badger
>         Attachments: TEZ-3554.001.patch
> Currently the Tez UI shows a link for task attempt logs on multiple different 
> pages. While the job is running this goes directly to the syslog of that 
> particular task attempt. There is no easy way to get to the other logs such 
> as stderr and stdout while the job is running. It would be useful to add a 
> link so that we can get to both the aggregated page of all of the logs as 
> well as having the link to go straight to the task attempt logs. 

This message was sent by Atlassian JIRA

Reply via email to