Roll recipe dependencies (trivial).

This is an automated CL created by the recipe roller. This CL rolls
recipe changes from upstream projects (chromiumos_config, recipe_engine) into this repository.

The build that created this CL was
https://ci.chromium.org/b/8738219551324599057

chromiumos_config:
https://chromium.googlesource.com/chromiumos/config.git/+log/982784e791dca41809165bb04397f4c821f3f6d7~..e14bad4b6f4d68cb3f94955f858befedca2402c9
  982784e (chromeos-ci-prod@chromeos-bot.iam.gserviceaccount.com)
      centralized_suites: automatic sync from autotest
  a3cabdb (chromeos-ci-prod@chromeos-bot.iam.gserviceaccount.com)
      centralized_suites: automatic sync from autotest
  19405f3 (chromeos-ci-prod@chromeos-bot.iam.gserviceaccount.com)
      centralized_suites: automatic sync from autotest
  2c43c79 (chromeos-ci-prod@chromeos-bot.iam.gserviceaccount.com)
      centralized_suites: automatic sync from autotest
  51182b1 (zhihuixie@google.com)
      test_result_proto: add a flag to identify AL test results
  ddae39f (chromeos-ci-prod@chromeos-bot.iam.gserviceaccount.com)
      centralized_suites: automatic sync from autotest
  e14bad4 (chromeos-ci-prod@chromeos-bot.iam.gserviceaccount.com)
      centralized_suites: automatic sync from autotest

recipe_engine:
https://chromium.googlesource.com/infra/luci/recipes-py.git/+/64ac83a80ac3909130275fd535ab2f03265a73a1
  64ac83a (iannucci@chromium.org)
      Switch execution details step to be a debug log.

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: I8dd0e7d5c448db24038f9165f0565eba54a1ee81
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/infra/proto/+/5827982
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>
1 file changed
tree: 4c28e0f7e85d5b41e20072f5ab993cb6dd55e8d0
  1. bin/
  2. extern/
  3. gen/
  4. go/
  5. infra/
  6. recipes/
  7. src/
  8. .gitattributes
  9. .gitignore
  10. buf.yaml
  11. generate.sh
  12. LICENSE
  13. OWNERS
  14. OWNERS.tse
  15. PRESUBMIT.cfg
  16. PRESUBMIT.py
  17. README.md
  18. setup_cipd.sh
  19. unblocked_terms.txt
README.md

infra/proto

infra/proto vs chromite/infra/proto

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.