Skip to content
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

Collect coverage from cc_binary data deps of java_test #15216

Merged
merged 1 commit into from
May 9, 2022

Conversation

fmeum
Copy link
Collaborator

@fmeum fmeum commented Apr 12, 2022

Before this commit, if a java_test executed a cc_binary from its data
deps, coverage for this cc_binary would not be collected. This is fixed
by adding the implicit $collect_cc_coverage attribute to
BazelJavaTestRule, similar to how this is already done for
BazelShTestRule.

Fixes the Java part of #15098.

Closes #15096.

PiperOrigin-RevId: 438785232

Fixes #15216

@fmeum fmeum requested a review from ckolli5 as a code owner April 12, 2022 06:32
@fmeum
Copy link
Collaborator Author

fmeum commented Apr 12, 2022

@Wyverald I tried to use @bazel-io fork 5.2.0, but it keeps failing both from issues and PRs: #15098 (comment)
#15096 (comment)

@fmeum fmeum force-pushed the release-5.2.0-15096 branch 2 times, most recently from 94aa451 to 3c56ba4 Compare April 13, 2022 13:12
@fmeum
Copy link
Collaborator Author

fmeum commented Apr 13, 2022

The CI failure is persistent, but looks quite unrelated.

@ckolli5
Copy link

ckolli5 commented Apr 19, 2022

Hi @fmeum, Can you please check the buildkite presubmit failures. Thanks!

@ckolli5 ckolli5 added the awaiting-user-response Awaiting a response from the author label Apr 19, 2022
Before this commit, if a java_test executed a cc_binary from its data
deps, coverage for this cc_binary would not be collected. This is fixed
by adding the implicit `$collect_cc_coverage` attribute to
BazelJavaTestRule, similar to how this is already done for
BazelShTestRule.

Fixes the Java part of bazelbuild#15098.

Closes bazelbuild#15096.

PiperOrigin-RevId: 438785232
@fmeum
Copy link
Collaborator Author

fmeum commented Apr 20, 2022

@ckolli5 I don't see how the failing test would be related to this PR. Is it possible that this is an issue with the remote execution test setup? test_remote_grpc_via_unix_socket_proxy fails with connection failures and doesn't have anything to do with coverage or java_test.

@ckolli5 ckolli5 removed the awaiting-user-response Awaiting a response from the author label May 9, 2022
@ckolli5 ckolli5 merged commit 96b126e into bazelbuild:release-5.2.0 May 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants