Revert "chromite: Remove plain failed_packages fields"

This reverts commit e9bce3db8631151f20d0e17458cc0304b07989c4.

Reason for revert: b/257551894 I believe this broke the recipe roller because one BuildTargetUnitTestResponse.failed_packages is still used

Original change's description:
> chromite: Remove plain failed_packages fields
> Since we've migrated relevant endpoints to using a FailedPackageData
> field and some time has passed, delete and reserve the fields.
> BUG=b:206514844
> TEST=./generate --allow-breaking
> Change-Id: If8345f0041b087d8418b15f7c73d3f3215dcedfb
> Reviewed-on:
> Reviewed-by: Cindy Lin <>
> Auto-Submit: Lizzy Presland <>
> Commit-Queue: Cindy Lin <>

Bug: b:206514844
Change-Id: I220c592f67fcf0351df5d8f916ee0f6b48d6eb86
Reviewed-by: George Engelbrecht <>
Commit-Queue: George Engelbrecht <>
Auto-Submit: Madeleine Hardt <>
5 files changed
tree: ee948cdd4ecbdf523974185c4fa85644bcb01399
  1. extern/
  2. gen/
  3. go/
  4. infra/
  5. recipes/
  6. src/
  7. .gitattributes
  8. .gitignore
  9. buf.yaml
  12. OWNERS
  13. PRESUBMIT.cfg
  17. unblocked_terms.txt


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.