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

Use gcov for collecting code coverage for gcc #5880

Closed
iirina opened this Issue Aug 14, 2018 · 1 comment

Comments

Projects
None yet
2 participants
@iirina
Copy link
Contributor

iirina commented Aug 14, 2018

Currently C++ coverage is 2x slower than just running the corresponding tests. The goal is to have similar times for running bazel test and bazel coverage on the same targets. When gcc is used gcov is the fastest tool for computing code coverage results.

@iirina

This comment has been minimized.

Copy link
Contributor

iirina commented Aug 28, 2018

Note: this should also work with clang but it needs some experimentation.

bazel-io pushed a commit that referenced this issue Sep 20, 2018

Add --experimental_cc_coverage flag.
This PR adds a new flag `--experimental_cc_coverage` that enables using `gcov` instead of `lcov` for collecting C++ code coverage.

Progress on #5880

Closes #5842.

RELNOTES: Faster coverage collection for gcc compiled C++ code can now be
tested by enabling it with --experimental_cc_coverage.
PiperOrigin-RevId: 213796978

@bazel-io bazel-io closed this in a77cf8b Oct 2, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment