[
https://issues.apache.org/jira/browse/HADOOP-4190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12634581#action_12634581
]
Hadoop QA commented on HADOOP-4190:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12390907/HADOOP-4190-v6.patch
against trunk revision 698721.
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 6 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 1 new Findbugs warnings.
+1 Eclipse classpath. The patch retains Eclipse classpath integrity.
+1 core tests. The patch passed core unit tests.
+1 contrib tests. The patch passed contrib unit tests.
Test results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3370/testReport/
Findbugs warnings:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3370/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3370/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3370/console
This message is automatically generated.
> Changes to JobHistory makes it backward incompatible
> ----------------------------------------------------
>
> Key: HADOOP-4190
> URL: https://issues.apache.org/jira/browse/HADOOP-4190
> Project: Hadoop Core
> Issue Type: Bug
> Components: mapred
> Reporter: Amar Kamat
> Assignee: Amar Kamat
> Priority: Blocker
> Fix For: 0.19.0
>
> Attachments: HADOOP-4190-v3.patch, HADOOP-4190-v4.patch,
> HADOOP-4190-v5.patch, HADOOP-4190-v6.patch
>
>
> With HADOOP-3245, the job history format has changed. Every log line now ends
> with a '.' (dot). JobHistory's parser will consider a history line valid only
> if it ends in a dot
> Hence the new parser wont be able to parse old history files.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
