[
https://issues.apache.org/jira/browse/MAPREDUCE-5746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13899182#comment-13899182
]
Hadoop QA commented on MAPREDUCE-5746:
--------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12628488/MAPREDUCE-5746-v2.patch
against trunk revision .
{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 1.3.9) 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-core
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-hs.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/4354//testReport/
Console output:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/4354//console
This message is automatically generated.
> Job diagnostics can implicate wrong task for a failed job
> ---------------------------------------------------------
>
> Key: MAPREDUCE-5746
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-5746
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: jobhistoryserver
> Affects Versions: 0.23.10, 2.1.1-beta
> Reporter: Jason Lowe
> Assignee: Jason Lowe
> Attachments: MAPREDUCE-5746-v2.patch, MAPREDUCE-5746.patch
>
>
> We've seen a number of cases where the history server is showing the wrong
> task as the reason a job failed. For example, "Task
> task_1383802699973_515536_m_027135 failed 1 times" when some other task had
> failed 4 times and was the real reason the job failed.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
