[
https://issues.apache.org/jira/browse/HADOOP-6009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12752094#action_12752094
]
Hadoop QA commented on HADOOP-6009:
-----------------------------------
+1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12418796/HADOOP-6009.patch
against trunk revision 812031.
+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 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 passed core unit tests.
+1 contrib tests. The patch passed contrib unit tests.
Test results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h4.grid.sp2.yahoo.net/21/testReport/
Findbugs warnings:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h4.grid.sp2.yahoo.net/21/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h4.grid.sp2.yahoo.net/21/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h4.grid.sp2.yahoo.net/21/console
This message is automatically generated.
> S3N listStatus incorrectly returns null instead of empty array when called on
> empty root
> ----------------------------------------------------------------------------------------
>
> Key: HADOOP-6009
> URL: https://issues.apache.org/jira/browse/HADOOP-6009
> Project: Hadoop Common
> Issue Type: Bug
> Components: fs/s3
> Affects Versions: 0.18.3
> Reporter: Ian Nowland
> Assignee: Ian Nowland
> Fix For: 0.21.0
>
> Attachments: HADOOP-6009-0.patch, HADOOP-6009.patch
>
>
> Null means the directory does not exist, which is obviously not the case.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
