[
https://issues.apache.org/jira/browse/MAPREDUCE-3349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13161925#comment-13161925
]
Hadoop QA commented on MAPREDUCE-3349:
--------------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12505869/MAPREDUCE-3349-v1.4.patch
against trunk revision .
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 9 new or modified tests.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
-1 findbugs. The patch appears to introduce 12 new Findbugs (version
1.3.9) warnings.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
+1 core tests. The patch passed unit tests in .
+1 contrib tests. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/1386//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/1386//artifact/trunk/hadoop-mapreduce-project/patchprocess/newPatchFindbugsWarningshadoop-mapreduce-examples.html
Console output:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/1386//console
This message is automatically generated.
> No rack-name logged in JobHistory for unsuccessful tasks
> --------------------------------------------------------
>
> Key: MAPREDUCE-3349
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3349
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2
> Affects Versions: 0.23.0
> Reporter: Vinod Kumar Vavilapalli
> Assignee: Devaraj K
> Priority: Blocker
> Fix For: 0.23.1
>
> Attachments: MAPREDUCE-3349-v1.4.patch, MAPREDUCE-3349.patch
>
>
> Found this while running jobs on a cluster with [~Karams].
> This is because TaskAttemptUnsuccessfulCompletionEvent history record doesn't
> have a rack field.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
