You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Beam JIRA Bot (Jira)" <ji...@apache.org> on 2021/10/05 17:25:01 UTC

[jira] [Commented] (BEAM-12651) Improve the accuracy of Java code coverage reporting

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

Beam JIRA Bot commented on BEAM-12651:
--------------------------------------

This issue was marked "stale-P2" and has not received a public comment in 14 days. It is now automatically moved to P3. If you are still affected by it, you can comment and move it back to P2.

> Improve the accuracy of Java code coverage reporting
> ----------------------------------------------------
>
>                 Key: BEAM-12651
>                 URL: https://issues.apache.org/jira/browse/BEAM-12651
>             Project: Beam
>          Issue Type: Improvement
>          Components: sdk-java-core
>            Reporter: Kiley Sok
>            Priority: P3
>
> Report more accurate code coverage numbers across projects
> https://ci-beam.apache.org/job/beam_PreCommit_Java_Cron/4284/jacoco/
> Remove from Jacoco report:
> generated protos (e.g. org.apache.beam.model.*, org.apache.beam.runners.dataflow.worker.windmill)
> groovy files (e.g. org.apache.beam.gradle)
> auto generated classes (e.g. AutoValue)



--
This message was sent by Atlassian Jira
(v8.3.4#803005)