[
https://issues.apache.org/jira/browse/HADOOP-3501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12602767#action_12602767
]
Hadoop QA commented on HADOOP-3501:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12383471/HADOOP-3051.patch
against trunk revision 663487.
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified
tests.
Please justify why no tests are needed for this patch.
+1 javadoc. The javadoc tool did not generate any warning messages.
-1 javac. The applied patch generated 455 javac compiler warnings (more
than the trunk's current 452 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 failed contrib unit tests.
Test results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2593/testReport/
Findbugs warnings:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2593/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2593/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2593/console
This message is automatically generated.
> deprecate InMemoryFileSystem
> ----------------------------
>
> Key: HADOOP-3501
> URL: https://issues.apache.org/jira/browse/HADOOP-3501
> Project: Hadoop Core
> Issue Type: Improvement
> Components: fs
> Affects Versions: 0.17.0
> Reporter: Doug Cutting
> Fix For: 0.18.0
>
> Attachments: HADOOP-3051.patch
>
>
> As of HADOOP-2095, InMemoryFileSystem is no longer used. Its design was
> optimized for a particular application and it is thus not a good
> general-purpose RAM-based FileSystem implementation, so it ought to be
> removed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
