You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Ryan Skraba (Jira)" <ji...@apache.org> on 2019/10/11 14:33:00 UTC
[jira] [Commented] (BEAM-6496) No coverage reported for
sdks/java/extensions/sql, due to class does not match errors
[ https://issues.apache.org/jira/browse/BEAM-6496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16949506#comment-16949506 ]
Ryan Skraba commented on BEAM-6496:
-----------------------------------
Hello! I just gave this a try, and can't reproduce today (b288d5af2289a0621f944c2d4bc271a0d8f786b7).
I picked a "random" commit from around the time period that it was reported (8298b553e0c5c5af703aac72a0150334696738e0), and I can reproduce it there... Didn't bother bisecting to find out exactly _why_
It looks like this can be closed.
> No coverage reported for sdks/java/extensions/sql, due to class does not match errors
> -------------------------------------------------------------------------------------
>
> Key: BEAM-6496
> URL: https://issues.apache.org/jira/browse/BEAM-6496
> Project: Beam
> Issue Type: Bug
> Components: build-system
> Reporter: Alan Myrvold
> Priority: Major
>
> Ran
> ./gradlew -p sdks/java/extensions/sql test jacocoTestReport
> but there were errors like:
> Execution data for class org/apache/beam/sdk/extensions/sql/impl/transform/BeamSqlOutputToConsoleFn does not match
> And the coverage report had all zeros.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)