You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Konrad Windszus (Jira)" <ji...@apache.org> on 2024/12/21 14:43:00 UTC

[jira] [Resolved] (OAK-11320) JaCoCo check fails when executing both ITs and UTs

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

Konrad Windszus resolved OAK-11320.
-----------------------------------
    Resolution: Invalid

As it turned out it was only an incompatibility between profile {{javadoc}} and the build with line coverage. This is fixed in the context of OAK-11319.

> JaCoCo check fails when executing both ITs and UTs 
> ---------------------------------------------------
>
>                 Key: OAK-11320
>                 URL: https://issues.apache.org/jira/browse/OAK-11320
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>            Reporter: Konrad Windszus
>            Priority: Major
>
> When executing a build with integration tests enabled (with profile {{integrationTesting}}) and profile {{javadoc}} enabled as well the coverage check introduced with OAK-5623 fails, as both ITs and UTs report to the same file {{./target/coverage-reports/jacoco-ut.exec}}. In order to have correct results both should be merged (via https://www.eclemma.org/jacoco/trunk/doc/merge-mojo.html) prior the check.
> Update: Surprisingly the conflicting data execution file between UTs and ITs are no issue, but the problem is that only a single UT is executed with profile {{javadoc}}: https://github.com/apache/jackrabbit-oak/blob/437375bdc9eb5207b6019587f9a21d6d018ff9bf/oak-parent/pom.xml#L1072
> Update2: The default for [append|https://www.eclemma.org/jacoco/trunk/doc/prepare-agent-mojo.html#append] is true, i.e. both ITs and UTs are aggregated in the same file. However this is not documented: https://github.com/jacoco/jacoco/issues/1676.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)