[
https://issues.apache.org/jira/browse/MAPREDUCE-3237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13139683#comment-13139683
]
Hadoop QA commented on MAPREDUCE-3237:
--------------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12501518/MAPREDUCE-3237-consolidated.patch
against trunk revision .
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 11 new or modified tests.
-1 javadoc. The javadoc tool appears to have generated 1 warning messages.
-1 javac. The applied patch generated 1800 javac compiler warnings (more
than the trunk's current 1712 warnings).
+1 findbugs. The patch does not introduce any 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/1206//testReport/
Console output:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/1206//console
This message is automatically generated.
> Move LocalJobRunner to hadoop-mapreduce-client-core module
> ----------------------------------------------------------
>
> Key: MAPREDUCE-3237
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3237
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: client
> Reporter: Tom White
> Assignee: Tom White
> Fix For: 0.23.0, 0.24.0
>
> Attachments: MAPREDUCE-3237-consolidated.patch,
> MAPREDUCE-3237-consolidated.patch, MAPREDUCE-3237.patch, MAPREDUCE-3237.patch
>
>
> LocalJobRunner works independently of MR1 (jobtracker and tasktrackers) and
> MR2 (YARN). The MR1 directory is being kept around only to support unit
> tests, so LocalJobRunner should be moved out to somewhere more permanent.
--
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
