[
https://issues.apache.org/jira/browse/MAPREDUCE-1309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12834583#action_12834583
]
Hadoop QA commented on MAPREDUCE-1309:
--------------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12436044/mapreduce-1309--2010-02-16-a.patch
against trunk revision 910465.
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 17 new or modified tests.
-1 javadoc. The javadoc tool appears to have generated 1 warning messages.
-1 javac. The applied patch generated 2219 javac compiler warnings (more
than the trunk's current 2215 warnings).
+1 findbugs. The patch does not introduce any new Findbugs warnings.
+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/Mapreduce-Patch-h6.grid.sp2.yahoo.net/458/testReport/
Findbugs warnings:
http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-h6.grid.sp2.yahoo.net/458/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-h6.grid.sp2.yahoo.net/458/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-h6.grid.sp2.yahoo.net/458/console
This message is automatically generated.
> I want to change the rumen job trace generator to use a more modular internal
> structure, to allow for more input log formats
> -----------------------------------------------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-1309
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1309
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Reporter: Dick King
> Assignee: Dick King
> Attachments: demuxer-plus-concatenated-files--2009-12-21.patch,
> demuxer-plus-concatenated-files--2010-01-06.patch,
> demuxer-plus-concatenated-files--2010-01-08-b.patch,
> demuxer-plus-concatenated-files--2010-01-08-c.patch,
> demuxer-plus-concatenated-files--2010-01-08-d.patch,
> demuxer-plus-concatenated-files--2010-01-08.patch,
> demuxer-plus-concatenated-files--2010-01-11.patch,
> mapreduce-1309--2009-01-14-a.patch, mapreduce-1309--2009-01-14.patch,
> mapreduce-1309--2010-01-20.patch, mapreduce-1309--2010-02-03.patch,
> mapreduce-1309--2010-02-04.patch, mapreduce-1309--2010-02-10.patch,
> mapreduce-1309--2010-02-12.patch, mapreduce-1309--2010-02-16-a.patch,
> mapreduce-1309--2010-02-16.patch
>
>
> There are two orthogonal questions to answer when processing a job tracker
> log: how will the logs and the xml configuration files be packaged, and in
> which release of hadoop map/reduce were the logs generated? The existing
> rumen only has a couple of answers to this question. The new engine will
> handle three answers to the version question: 0.18, 0.20 and current, and two
> answers to the packaging question: separate files with names derived from the
> job ID, and concatenated files with a header between sections [used for
> easier file interchange].
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
