Get `bazel coverage` to work with Pigweed toolchains [304833225]

Assigned

Feature Request

Status Update

No update yet.

Description

tp...@google.com

created issue #1

Oct 11, 2023 09:36PM

We used to support collecting code coverage with Bazel, but dropped toolchain support for it when we switched to our own toolchain configuration in https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/164824.

Comments

tp...@google.com <tp...@google.com> #2Oct 11, 2023 09:37PM

We may need a feature similar to https://github.com/bazelembedded/rules_cc_toolchain/blob/9f209fda87414285bc66accd3612575b29760fba/cc_toolchain/features/BUILD.bazel#L91-L103

ap...@google.com <ap...@google.com> #3Dec 11, 2023 05:46PM

Project: pigweed/pigweed
Branch: main

commit f3899e6bb5318a269566d1ce600ec995bc999908
Author: Ted Pudlik <tpudlik@google.com>
Date: Mon Dec 11 17:43:55 2023

docs: Add Bazel code coverage TODO

Bug:

b/304833225

Change-Id: I245a2bd21232dcffa3bb3cb889015e5115ad7b66
Reviewed-on:

https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/182812
Reviewed-by: Alexei Frolov <frolv@google.com>
Presubmit-Verified: CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>
Commit-Queue: Ted Pudlik <tpudlik@google.com>

M docs/build_system.rst

https://pigweed-review.git.corp.google.com/182812

Issue 304833225

Description

Issue summary

Comments

tp...@google.com <tp...@google.com> #2Oct 11, 2023 09:37PM

ap...@google.com <ap...@google.com> #3Dec 11, 2023 05:46PM

Add comment

Issue metadata