[
https://issues.apache.org/jira/browse/MAPREDUCE-6316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14559576#comment-14559576
]
Gera Shegalov commented on MAPREDUCE-6316:
------------------------------------------
The checkstyle failure is benign:
{code}
tw-mbp-gshegalov hadoop-common (MAPREDUCE-6316.v3.patch)]$ diff <(cat
~/checkstyle-errors.xml | sed 's/line=\"[0-9]*\"//g') <(cat
./target/test/checkstyle-errors.xml | sed 's/line=\"[0-9]*\"//g')
51696c51696
< <error column="5" severity="error" message="Method length is 166 lines (max
allowed is 150)."
source="com.puppycrawl.tools.checkstyle.checks.sizes.MethodLengthCheck"/>
---
> <error column="5" severity="error" message="Method length is 165 lines (max
> allowed is 150)."
> source="com.puppycrawl.tools.checkstyle.checks.sizes.MethodLengthCheck"/>
{code}
Unit test failures are unrelated and pass locally:
- hadoop.mapreduce.v2.app.webapp.TestAppController
- hadoop.mapreduce.v2.app.webapp.TestAMWebServicesTasks
- hadoop.mapreduce.jobhistory.TestEvents
+1, will commit later tonight.
> 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, 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)
