Gergely Fábián

This is a Bazel bug: https://github.com/bazelbuild/bazel/pull/15081, and was already fixed on master. I guess a workaround is to rebuild jacocorunner from the fixed Bazel version and use that as a...

Use the updated `scripts/build_jacocorunner/build_jacocorunner_bazel_5.0+.sh` script to build a custom jacocorunner to work this issue around (will be merged in #1399, hopefully).

Here is the intended usage: https://github.com/gergelyfabian/rules_scala/commit/0cd31de8bc1b6f815afb7debde76aae959f855c5 We had a usecase, that we wanted to generate fat jars with "internal" and "external" dependencies separately (to be able to package them separately...

Another possible fix is: --instrumentation_filter="-:java_library"

The problem is, that without additional parameters I get only Java coverage. I need to disable instrumentation for java_library to get coverage for scala_library. I could also live with getting...

@jakemcc I believe the link you sent points to this very same issue. What could be the proper link?

Managed to create an example. E.g. to enable parallel execution of tests with scalatest: ``` scala_test( name = "my_test", srcs = [ ... ], args = [ "-P", ], )...

A workaround may be to set in `.bazelrc` the following flag: ``` coverage --build_tests_only ``` In that case `bazel coverage //...` won't build (incorrectly) targets that I do not need...

Hi @liucijus :) The strange thing is, that in my example repo (https://github.com/gergelyfabian/bazel-scala-example) I cannot reproduce this error (I've just upgraded it to the latest rules_scala and Scala 2.13). Will...

I think I have the reproduction, just let me clean it up, and will upload it as a branch to my example repo.