[
https://issues.apache.org/jira/browse/MAPREDUCE-1518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12841677#action_12841677
]
Hadoop QA commented on MAPREDUCE-1518:
--------------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12437948/MAPREDUCE-1518.0.patch
against trunk revision 919173.
+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 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-h4.grid.sp2.yahoo.net/20/testReport/
Findbugs warnings:
http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-h4.grid.sp2.yahoo.net/20/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-h4.grid.sp2.yahoo.net/20/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-h4.grid.sp2.yahoo.net/20/console
This message is automatically generated.
> On contrib/raid, the RaidNode currently runs the deletion check for parity
> files on directories too. It would be better if it didn't.
> -------------------------------------------------------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-1518
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1518
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: contrib/raid
> Environment: On contrib/raid, the RaidNode currently runs the
> deletion check for parity files on directories too. It runs okay because the
> directory is not empty and trying to delete it non-recursively fails, but
> such failure messages only polute the log file.
> My proposal is the following:
> If recursePurge is checking a directory, it should call itself recursively.
> If it's checking a file, it should do the deletion check.
> Reporter: Rodrigo Schmidt
> Assignee: Rodrigo Schmidt
> Attachments: MAPREDUCE-1518.0.patch
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
