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

Hadoop QA commented on MAPREDUCE-6316:
--------------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12726701/MAPREDUCE-6316.v2.patch
  against trunk revision c92f6f3.

    {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 eclipse:eclipse{color}.  The patch built with 
eclipse:eclipse.

    {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 
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-hs 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common.

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

This message is automatically generated.

> Task Attempt List entries should link to the task overview
> ----------------------------------------------------------
>
>                 Key: MAPREDUCE-6316
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-6316
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>            Reporter: Siqi Li
>            Assignee: Siqi Li
>         Attachments: All Attempts page.png, MAPREDUCE-6316.v1.patch, 
> MAPREDUCE-6316.v2.patch, Task Overview page.png
>
>
> Typical workflow is to click on the list of failed attempts. Then you want to 
> look at the counters, or the list of attempts of just one task in general. If 
> each entry task attempt id linked the task id portion of it back to the task, 
> we would not have to go through the list of tasks to search for the task.



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

Reply via email to