Skip to content

Conversation

@fmeum
Copy link
Collaborator

@fmeum fmeum commented Dec 12, 2022

When coverage is disabled, cc_test should not depend on the Java LCOV merger tool. This is achieved by using configuration_field.

Also depend on coverage tools in exec rather than target configuration, matching Java rules as well as the once-per-build coverage report generator.

Fixes #16961

When coverage is disabled, `cc_test` should not depend on the Java LCOV
merger tool. This is achieved by using `configuration_field`.

Also depend on coverage tools in `exec` rather than `target`
configuration, matching Java rules.
@fmeum
Copy link
Collaborator Author

fmeum commented Dec 12, 2022

@buildbreaker2021 Can you review?

@buildbreaker2021 buildbreaker2021 added the awaiting-PR-merge PR has been approved by a reviewer and is ready to be merge internally label Dec 12, 2022
@sgowroji sgowroji added the team-Rules-Server Issues for serverside rules included with Bazel label Dec 13, 2022
@fmeum fmeum deleted the 16961-cc-test-optional-coverage branch December 13, 2022 08:31
fmeum added a commit to fmeum/bazel that referenced this pull request Dec 13, 2022
When coverage is disabled, `cc_test` should not depend on the Java LCOV merger tool. This is achieved by using `configuration_field`.

Also depend on coverage tools in `exec` rather than `target` configuration, matching Java rules as well as the once-per-build coverage report generator.

Fixes bazelbuild#16961

Closes bazelbuild#16994.

PiperOrigin-RevId: 494941601
Change-Id: Ie614de713b87bb66d869515676698f1a71cb106e
@sgowroji sgowroji removed the awaiting-PR-merge PR has been approved by a reviewer and is ready to be merge internally label Dec 13, 2022
meteorcloudy pushed a commit that referenced this pull request Dec 13, 2022
When coverage is disabled, `cc_test` should not depend on the Java LCOV merger tool. This is achieved by using `configuration_field`.

Also depend on coverage tools in `exec` rather than `target` configuration, matching Java rules as well as the once-per-build coverage report generator.

Fixes #16961

Closes #16994.

PiperOrigin-RevId: 494941601
Change-Id: Ie614de713b87bb66d869515676698f1a71cb106e
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

team-Rules-Server Issues for serverside rules included with Bazel

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Unable to build x86 based unit tests with bazel 6.0.0rc4 because there is no x86 based remote java toolchain

4 participants