[
https://issues.apache.org/jira/browse/MAPREDUCE-4646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13452459#comment-13452459
]
Hadoop QA commented on MAPREDUCE-4646:
--------------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12544528/MAPREDUCE-4646.patch
against trunk revision .
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 3 new or modified test
files.
-1 javac. The patch appears to cause the build to fail.
Console output:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/2838//console
This message is automatically generated.
> client does not receive job diagnostics for failed jobs
> -------------------------------------------------------
>
> Key: MAPREDUCE-4646
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4646
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2
> Affects Versions: 0.23.0, 2.0.1-alpha
> Reporter: Jason Lowe
> Assignee: Jason Lowe
> Attachments: MAPREDUCE-4646.patch, MAPREDUCE-4646.patch
>
>
> When a job fails the client is not showing any diagnostics. For example,
> running a fail job results in this not-so-helpful message from the client:
> {noformat}
> 2012-09-07 21:12:00,649 INFO [main] mapreduce.Job
> (Job.java:monitorAndPrintJob(1308)) - Job job_1347052207658_0001 failed with
> state FAILED due to:
> {noformat}
> ...and nothing else to go with it indicating what went wrong. The job
> diagnostics are apparently not making it back to the client.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
