hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Konstantin Boudnik (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HDFS-783) libhdfs tests brakes code coverage runs with Clover
Date Tue, 24 Nov 2009 20:35:40 GMT

     [ https://issues.apache.org/jira/browse/HDFS-783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Konstantin Boudnik updated HDFS-783:
------------------------------------

    Attachment: HDFS-783.patch

Turns out that I've done the patch for the outdated version of the shell script. This new
version is the same as before but put one of the lines to a different spot.

Also, I've ran {{test-patch}} locally and all seems to be ok:
{noformat}
There appear to be 125 release audit warnings before the patch and 125 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 4 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.
{noformat}

I've started {{ant clover test}} run locally and now it passes without a glitch, i.e. c++
compilation is went through and libhdfs test has passed. 


> libhdfs tests brakes code coverage runs with Clover
> ---------------------------------------------------
>
>                 Key: HDFS-783
>                 URL: https://issues.apache.org/jira/browse/HDFS-783
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: test
>    Affects Versions: 0.22.0
>            Reporter: Konstantin Boudnik
>            Assignee: Konstantin Boudnik
>         Attachments: HDFS-783.patch, HDFS-783.patch
>
>
> libhdfs test is executed by a script which sets a certain environment for every run.
While standalone execution works well, code coverage runs are broken by this test because
it tries to executed an instrumented Hadoop code without having clover.jar in its classpath.

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


Mime
View raw message