-
-
Notifications
You must be signed in to change notification settings - Fork 286
rules_scala coverage doesn't work with bazel 0.24.0 and later #798
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
In bazel 0.24 the flag |
The test log has no errors. The intermediate jcov.dat file is empty. Running with
looks like an error that should be fixed in more recent bazel versions |
I seem to remember trying with 0.28 and finding the same breakage. |
What breakage were you seeing? The test itself doesn't use instrumentation filter and it only fails because of mismatched expected and actual coverage report. |
|
With 0.27 and 0.28 there is also a mismatch between the jacoco version in rules_scala and in bazel, so that must be fixed as well.
Yes but the actual culprit may be different. Running the test as is doesn't offer any details about the breakages other than "it doesn't work". |
Too many changes overflow. 😞 Since 0.24 JacocoCoverageRunner moved out of bazel to remote_java_tools and since 0.25 the CoverageOutputGenerator moved out of bazel to another remote repository, which makes this hard to debug. |
I'll try to look more into this when I have more time, since the tests are now passing at head. For now I'm a bit swamped with bazel 1.0 work. |
Yeah, let's not do more work than is strictly necessary for Bazel 1.0. I rebased #793 and I hope that'll be enough to turn Travis green. |
Hi @d-haxton I saw your PR and was very grateful you made it work for Scala! Otherwise we'd be in a serious fire fighting mode right now :) There's some information lost somewhere, but didn't figure out where. |
@d-haxton @iirina
|
@iirina when and where the fix will be available. Can i try some RC and let you know ? |
As of java_tools javac11-v4.0 the releases are also uploaded on Github under [the java_tools repository](https://github.com/bazelbuild/java_tools/releases). Add the additional Github urls to make downloading the archives more reliable. Users have reported `connection reset` errors from the mirror.bazel urls (for example bazel-contrib/rules_scala#798 (comment)). Closes #9266. PiperOrigin-RevId: 265884330
@d-haxton @iirina
|
outputs an empty
bazel-testlogs/test/coverage/test-all/coverage.dat
The text was updated successfully, but these errors were encountered: