| commit | 3166e232f425fa4d912a30f6256cb29741f425ae | [log] [tgz] |
|---|---|---|
| author | Srinivas Hegde <srinivashegde@google.com> | Mon Sep 12 21:38:45 2022 +0000 |
| committer | Chromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Sep 15 19:15:45 2022 +0000 |
| tree | 2229a3c3081a8619d6954b5a5a24770c95bdf6ca | |
| parent | 0884c4d360ce21addd837c601c000edcb47b5a44 [diff] |
proto: Add option to collect code coverage for rust. At present, we use the coverage USE flag to find code coverage. But, rust packages are incompatible with the underlying tools and need to use a separate USE flag and only need to trigger rust packages. Add a new fag to the build request to handle rust packages BUG=b:246409134 TEST=presubmits Change-Id: Icee7a7b74d64abfd9f6a9087ad8127e510ce764b Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/infra/proto/+/3892792 Reviewed-by: Cindy Lin <xcl@google.com> Commit-Queue: Srinivas Hegde <srinivashegde@google.com>
This repository exists in two locations in the tree: infra/proto, and chromite/infra/proto. The infra/proto repository is always at ToT, while the chromite/infra/proto checkout is branched to allow the proto there to (more) accurately reflect the version of the proto the Build API is using.
When making changes to the proto that you need to test in the Build API, you will need ensure the changes are applied to the chromite/infra/proto checkout. Chromite generates its proto bindings from the chromite/infra/proto repo.