[ 
https://issues.apache.org/jira/browse/HADOOP-10035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13792057#comment-13792057
 ] 

Hadoop QA commented on HADOOP-10035:
------------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12607893/HADOOP-10035.2.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

    {color:green}+1 tests included{color}.  The patch appears to include 1 new 
or modified test files.

    {color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

    {color:green}+1 javadoc{color}.  The javadoc tool did not generate any 
warning messages.

    {color:green}+1 eclipse:eclipse{color}.  The patch built with 
eclipse:eclipse.

    {color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 1.3.9) warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in 
hadoop-common-project/hadoop-common.

    {color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-HADOOP-Build/3204//testReport/
Console output: 
https://builds.apache.org/job/PreCommit-HADOOP-Build/3204//console

This message is automatically generated.

> Cleanup TestFilterFileSystem
> ----------------------------
>
>                 Key: HADOOP-10035
>                 URL: https://issues.apache.org/jira/browse/HADOOP-10035
>             Project: Hadoop Common
>          Issue Type: Improvement
>    Affects Versions: 2.1.1-beta
>            Reporter: Suresh Srinivas
>            Assignee: Suresh Srinivas
>         Attachments: HADOOP-10035.1.patch, HADOOP-10035.2.patch, 
> HADOOP-10035.patch
>
>
> Currently TestFilterFileSystem only checks for FileSystem methods that must 
> be implemented in FilterFileSystem with a list of methods that are exception 
> to this rule. This jira wants to make this check stricter by adding a test 
> for ensuring the methods in exception rule list must not be implemented by 
> the FilterFileSystem.
> This also cleans up the current class that has methods from exception rule 
> list to interface to avoid having to provide dummy implementation of the 
> methods.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Reply via email to