Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Message-ID: <283413697.1255066411282.JavaMail.jira@brutus>
Date: Thu, 8 Oct 2009 22:33:31 -0700 (PDT)
From: "Konstantin Boudnik (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Subject: [jira] Commented: (HADOOP-6204) Implementing aspects development
 and fault injeciton framework for Hadoop
In-Reply-To: <1837050058.1250629394943.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Konstantin Boudnik commented on HADOOP-6204:
--------------------------------------------

I'm running test-patch and getting this
{noformat}
There appear to be 0 release audit warnings before the patch and 1 release audit warnings after applying the patch.


-1 overall.

    +1 @author.  The patch does not contain any @author tags.

    +1 tests included.  The patch appears to include 20 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 generated 1 release audit warnings (more than the trunk's current 0 warnings).

{noformat}

However, that warning looks totally weird for me:
{noformat}
     [exec]   Copying the various non-generated resources to site.
     [exec]   Warnings will be issued if the optional project resources are not found.
     [exec]   This is often the case, because they are optional and so may not be available.
     [exec] Copying project resources and images to site ...
     [exec] Warning: /Users/xxx/work/Common.test/src/docs/build/webapp/resources not found.
     [exec] Copying main skin images to site ...
     [exec] Copying 18 files to /Users/xxx/work/Common.test/src/docs/build/site/skin/images
     [exec] Copying 14 files to /Users/xxx/work/Common.test/src/docs/build/site/skin/images
     [exec] Copying project skin images to site ...
     [exec] Warning: /Users/xxx/work/Common.test/src/docs/src/documentation/skins/common/images not found.
     [exec] Warning: /Users/xxx/work/Common.test/src/docs/src/documentation/skins/pelt/images not found.
     [exec] Copying main skin css and js files to site ...
     [exec] Copying 11 files to /Users/xxx/work/Common.test/src/docs/build/site/skin
     [exec] Copying 4 files to /Users/xxx/work/Common.test/src/docs/build/site/skin
     [exec] Copying project skin css and js files to site ...
     [exec] Warning: /Users/xxx/work/Common.test/src/docs/src/documentation/skins/common not found.
     [exec] Warning: /Users/xxx/work/Common.test/src/docs/src/documentation/skins/pelt not found.
{noformat}

Apparently this patch has nothing to do with docs.

> Implementing aspects development and fault injeciton framework for Hadoop
> -------------------------------------------------------------------------
>
>                 Key: HADOOP-6204
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6204
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: build, test
>            Reporter: Konstantin Boudnik
>            Assignee: Konstantin Boudnik
>             Fix For: 0.21.0, 0.22.0
>
>         Attachments: HADOOP-6204.patch, HADOOP-6204.patch, HADOOP-6204.patch, HADOOP-6204.patch, HADOOP-6204.patch, HADOOP-6204.patch.indirect, HADOOP-6204.patch.withmacros
>
>
> Fault injection framework implementation in HDFS (HDFS-435) turns out to be a very useful feature both for error handling testing and for various simulations.
> There's certain demand for this framework, thus it need to be pulled up from HDFS and brought into Common, so other sub-projects will be able to share it if needed.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.