[
https://issues.apache.org/jira/browse/HADOOP-5392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12680141#action_12680141
]
Hadoop QA commented on HADOOP-5392:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12401600/HADOOP-5392-v2.3.patch
against trunk revision 751463.
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 3 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 does not introduce any new Findbugs warnings.
+1 Eclipse classpath. The patch retains Eclipse classpath integrity.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
-1 core tests. The patch failed core unit tests.
+1 contrib tests. The patch passed contrib unit tests.
Test results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-minerva.apache.org/34/testReport/
Findbugs warnings:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-minerva.apache.org/34/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-minerva.apache.org/34/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-minerva.apache.org/34/console
This message is automatically generated.
> JobTracker crashes during recovery if job files are garbled
> -----------------------------------------------------------
>
> Key: HADOOP-5392
> URL: https://issues.apache.org/jira/browse/HADOOP-5392
> Project: Hadoop Core
> Issue Type: Bug
> Components: mapred
> Reporter: Amar Kamat
> Assignee: Amar Kamat
> Priority: Blocker
> Fix For: 0.20.0
>
> Attachments: HADOOP-5392-v2.1.patch, HADOOP-5392-v2.3.patch
>
>
> Jobtracker crashed in the recovery stage for a job with 0 byte job.xml.
> Ideally one would expect the jobtracker to try and recover as many jobs as
> possible.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
