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 "Marcel Reutegger (Jira)" <ji...@apache.org> on 2023/03/02 14:43:00 UTC

[jira] [Commented] (OAK-10128) Disable coverage check for oak-jcr integration tests

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

Marcel Reutegger commented on OAK-10128:
----------------------------------------

Proposed changes to Jenkinsfile: https://github.com/apache/jackrabbit-oak/pull/864

> Disable coverage check for oak-jcr integration tests
> ----------------------------------------------------
>
>                 Key: OAK-10128
>                 URL: https://issues.apache.org/jira/browse/OAK-10128
>             Project: Jackrabbit Oak
>          Issue Type: Task
>          Components: jcr
>            Reporter: Marcel Reutegger
>            Assignee: Marcel Reutegger
>            Priority: Minor
>
> Many PR currently fail with oak-jcr:it complaining about insufficient branch coverage. 
> {noformat}
> [WARNING] Rule violated for bundle oak-jcr: branches covered ratio is 0.56, but expected minimum is 0.57
> {noformat}
> I'm not able to reproduce this locally and I'm also questioning whether we should enforce a coverage ratio on integration tests. PRs are configured to also run unit tests for oak-jcr as a separate module. In my view this is where coverage should be enforced, which is already the case.
> Therefore I suggest to disable coverage check for integration tests.



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