hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-6316) Task Attempt List entries should link to the task overview
Date Wed, 22 Apr 2015 19:21:59 GMT

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

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

\\
\\
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | pre-patch |  14m 34s | 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} | whitespace |   0m  0s | The patch has no lines that end in whitespace.
|
| {color:green}+1{color} | javac |   7m 26s | There were no new javac warning messages. |
| {color:green}+1{color} | javadoc |   9m 32s | 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 |   5m 32s | The applied patch generated  4  additional
checkstyle issues. |
| {color:green}+1{color} | install |   1m 32s | mvn install still works. |
| {color:green}+1{color} | eclipse:eclipse |   0m 32s | The patch built with eclipse:eclipse.
|
| {color:green}+1{color} | findbugs |   3m  1s | The patch does not introduce any new Findbugs
(version 2.0.3) warnings. |
| {color:red}-1{color} | mapreduce tests |  10m  9s | Tests failed in hadoop-mapreduce-client-app.
|
| {color:green}+1{color} | mapreduce tests |   5m 48s | Tests passed in hadoop-mapreduce-client-hs.
|
| {color:green}+1{color} | yarn tests |   1m 55s | Tests passed in hadoop-yarn-common. |
| | |  60m 28s | |
\\
\\
|| Reason || Tests ||
| Failed unit tests | hadoop.mapreduce.v2.app.webapp.TestAMWebServicesTasks |
|   | hadoop.mapreduce.jobhistory.TestEvents |
|   | hadoop.mapreduce.v2.app.webapp.TestAppController |
\\
\\
|| Subsystem || Report/Notes ||
| Patch URL | http://issues.apache.org/jira/secure/attachment/12727296/MAPREDUCE-6316.v3.patch
|
| Optional Tests | javadoc javac unit findbugs checkstyle |
| git revision | trunk / 1f4767c |
| checkstyle | https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/5432/artifact/patchprocess/checkstyle-result-diff.txt
|
| hadoop-mapreduce-client-app test log | https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/5432/artifact/patchprocess/testrun_hadoop-mapreduce-client-app.txt
|
| hadoop-mapreduce-client-hs test log | https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/5432/artifact/patchprocess/testrun_hadoop-mapreduce-client-hs.txt
|
| hadoop-yarn-common test log | https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/5432/artifact/patchprocess/testrun_hadoop-yarn-common.txt
|
| Test Results | https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/5432/testReport/
|
| Console output | https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/5432//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
>         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)

Mime
View raw message