[
https://issues.apache.org/jira/browse/HADOOP-8930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Joseph Evans updated HADOOP-8930:
----------------------------------------
Resolution: Fixed
Fix Version/s: 0.23.5
2.0.3-alpha
3.0.0
Status: Resolved (was: Patch Available)
Thanks Andrey,
I pulled this into trunk, branch-2, and branch-0.23.
> Cumulative code coverage calculation
> ------------------------------------
>
> Key: HADOOP-8930
> URL: https://issues.apache.org/jira/browse/HADOOP-8930
> Project: Hadoop Common
> Issue Type: Improvement
> Components: test
> Affects Versions: 0.23.3, 2.0.2-alpha
> Reporter: Andrey Klochkov
> Assignee: Andrey Klochkov
> Fix For: 3.0.0, 2.0.3-alpha, 0.23.5
>
> Attachments: HADOOP-8930-branch-0.23.patch, HADOOP-8930.patch
>
>
> When analyzing code coverage in Hadoop Core, we noticed that some coverage
> gaps are caused by the way the coverage calculation is done currently. More
> specifically, right now coverage can not be calculated for the whole Core at
> once, but can only be calculated separately for top level modules like
> common-project, hadoop-hdfs-project etc.
> At the same time, some code in particular modules is tested by tests in other
> modules of Core. For example, "org.apache.hadoop.fs" from
> hadoop-common-project/hadoop-common is not covered there but it's covered by
> tests under hadoop-hdfs-project.
> To enable calculation of "cumulative" code coverage it's needed to move
> Clover profile definition up one level, from hadoop-project/pom.xml to the
> top level pom.xml (hadoop-main).
> Patch both for 0.23 and 2.x will be attached shortly.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
