[
https://issues.apache.org/jira/browse/MAPREDUCE-2606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13052986#comment-13052986
]
Hadoop QA commented on MAPREDUCE-2606:
--------------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12483369/MAPREDUCE-2606.patch
against trunk revision 1137017.
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 5 new or modified tests.
+1 javadoc. The javadoc tool did not generate any warning messages.
-1 javac. The patch appears to cause tar ant target to fail.
+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 failed these core unit tests:
org.apache.hadoop.cli.TestMRCLI
org.apache.hadoop.fs.TestFileSystem
-1 contrib tests. The patch failed contrib unit tests.
+1 system test framework. The patch passed system test framework compile.
Test results:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/409//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/409//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/409//console
This message is automatically generated.
> IsolationRunner broken
> ----------------------
>
> Key: MAPREDUCE-2606
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-2606
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Reporter: Alejandro Abdelnur
> Assignee: Alejandro Abdelnur
> Attachments: MAPREDUCE-2606.patch
>
>
> IsolationRunner it seems it has been broken for a while, it gives a NPE when
> trying to use it.
> In addition, it supports only Map tasks; to use it the user must ssh to the
> node where the task failed; and unless the job has been configured to keep
> local files, the job must be run again.
> Because of this, IMO, the current implementation of IsolationRunner is not of
> much use.
> Any objection to remove it from trunk and if people have the need for such
> functionality to open another JIRA to build this functionality supported by
> the JobTracker (ie via the UI console)?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
