| commit | 92983e743bef2d5ff224e6969e232055793c7bc9 | [log] [tgz] |
|---|---|---|
| author | recipe-roller <recipe-mega-autoroller@chops-service-accounts.iam.gserviceaccount.com> | Thu Nov 17 12:23:38 2022 -0800 |
| committer | Chromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Nov 17 20:31:30 2022 +0000 |
| tree | f58a19bfad20d5c6cd0c591cfd3ab92893e7b945 | |
| parent | cc7efcfa40f419ddd7f2fcb1dba2194723f45b6e [diff] |
Roll recipe dependencies (trivial). This is an automated CL created by the recipe roller. This CL rolls recipe changes from upstream projects (recipe_engine) into this repository. The build that created this CL was https://ci.chromium.org/b/8797217680081518561 recipe_engine: https://chromium.googlesource.com/infra/luci/recipes-py.git/+/cd88b2f65f0d20ef10067be74368174bcb203806 cd88b2f (yuanjunh@google.com) [file] handle non-encodable string in listdir cmd Please check the following references for more information: - autoroller, https://chromium.googlesource.com/infra/luci/recipes-py/+/main/doc/workflow.md#autoroller - rollback, https://chromium.googlesource.com/infra/luci/recipes-py/+/main/doc/workflow.md#rollback - cross-repo dependencies, https://chromium.googlesource.com/infra/luci/recipes-py/+/main/doc/cross_repo.md Use https://goo.gl/noib3a to file a bug. Recipe-Tryjob-Bypass-Reason: Autoroller Ignore-Freeze: Autoroller Bugdroid-Send-Email: False Change-Id: I014b878811ecf8aabacb804be5f33bccfb1addeb Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/infra/proto/+/4035071 Bot-Commit: Recipe Roller <recipe-mega-autoroller@chops-service-accounts.iam.gserviceaccount.com> Commit-Queue: Recipe Roller <recipe-mega-autoroller@chops-service-accounts.iam.gserviceaccount.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.