Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Date: Thu, 28 May 2015 02:07:18 +0000 (UTC)
From: "Hadoop QA (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Message-ID: <JIRA.12820673.1428968219000.47447.1432778838101@Atlassian.JIRA>
In-Reply-To: <JIRA.12820673.1428968219000@Atlassian.JIRA>
References: <JIRA.12820673.1428968219000@Atlassian.JIRA>
 <JIRA.12820673.1428968219574@arcas>
Subject: [jira] [Commented] (MAPREDUCE-6316) Task Attempt List entries
 should link to the task overview
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

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

\\
\\
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | pre-patch |  15m 15s | Pre-patch trunk compilation is healthy. |
| {color:green}+1{color} | @author |   0m  0s | The patch does not contain any @author tags. |
| {color:red}-1{color} | tests included |   0m  0s | 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{color} | javac |   7m 46s | There were no new javac warning messages. |
| {color:green}+1{color} | javadoc |   9m 52s | There were no new javadoc warning messages. |
| {color:green}+1{color} | release audit |   0m 23s | The applied patch does not increase the total number of release audit warnings. |
| {color:red}-1{color} | checkstyle |   0m 46s | The applied patch generated  1 new checkstyle issues (total was 43, now 43). |
| {color:green}+1{color} | whitespace |   0m  0s | The patch has no lines that end in whitespace. |
| {color:green}+1{color} | install |   1m 35s | mvn install still works. |
| {color:green}+1{color} | eclipse:eclipse |   0m 32s | The patch built with eclipse:eclipse. |
| {color:red}-1{color} | findbugs |   1m 43s | The patch appears to introduce 1 new Findbugs (version 3.0.0) warnings. |
| {color:green}+1{color} | mapreduce tests |   9m 29s | Tests passed in hadoop-mapreduce-client-app. |
| {color:green}+1{color} | mapreduce tests |   5m 53s | Tests passed in hadoop-mapreduce-client-hs. |
| | |  53m 18s | |
\\
\\
|| Reason || Tests ||
| FindBugs | module:hadoop-mapreduce-client-app |
|  |  Inconsistent synchronization of org.apache.hadoop.mapreduce.v2.app.rm.RMContainerAllocator.reduceNodeLabelExpression; locked 66% of time  Unsynchronized access at RMContainerAllocator.java:66% of time  Unsynchronized access at RMContainerAllocator.java:[line 218] |
\\
\\
|| Subsystem || Report/Notes ||
| Patch URL | http://issues.apache.org/jira/secure/attachment/12735731/MAPREDUCE-6316.v5.patch |
| Optional Tests | javadoc javac unit findbugs checkstyle |
| git revision | trunk / 5450413 |
| checkstyle |  https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/5757/artifact/patchprocess/diffcheckstylehadoop-mapreduce-client-hs.txt |
| Findbugs warnings | https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/5757/artifact/patchprocess/newPatchFindbugsWarningshadoop-mapreduce-client-app.html |
| hadoop-mapreduce-client-app test log | https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/5757/artifact/patchprocess/testrun_hadoop-mapreduce-client-app.txt |
| hadoop-mapreduce-client-hs test log | https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/5757/artifact/patchprocess/testrun_hadoop-mapreduce-client-hs.txt |
| Test Results | https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/5757/testReport/ |
| Java | 1.7.0_55 |
| uname | Linux asf903.gq1.ygridcore.net 3.13.0-36-lowlatency #63-Ubuntu SMP PREEMPT Wed Sep 3 21:56:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux |
| Console output | https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/5757/console |


This message was 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
>              Labels: BB2015-05-TBR
>         Attachments: AM attempt page.png, AM task page.png, All Attempts page.png, MAPREDUCE-6316.v1.patch, MAPREDUCE-6316.v2.patch, MAPREDUCE-6316.v3.patch, MAPREDUCE-6316.v4.patch, MAPREDUCE-6316.v5.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)