[roll] Roll fuchsia [component] propagate errors when failing to retrieve bootfs entries

We previously observed (in CL 1393933) that when the component manager failed to receive the bootfs entries from userboot, it would report an error and continue trying to bootstrap itself.  This CL ensures that it would exit instead.

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1393914
Original-Revision: bcf6cd6d82f15d9e3fa247deeb3baf0eedd1d122
GitOrigin-RevId: 00a72b99d8e8f00ee59189f9838be0a8ff72e0f9
Change-Id: Ib5f0edf218555c7db182a5c6561d5af2798ba071
1 file changed
tree: 1900ae7573fdbceb79fa57eabaaf952c50c0b2b2
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. flower
  6. jiri.lock
  7. MILESTONE
  8. minimal
  9. prebuilts
  10. README.md
  11. stem
  12. test_durations
README.md

Integration

This repository contains Fuchsia's Global Integration manifest files.

Making changes

All changes should be made to the internal version of this repository. Our infrastructure automatically updates this version when the internal one changes.

Currently all changes must be made by a Google employee. Non-Google employees wishing to make a change can ask for assistance in one of the communication channels documented at get involved.

Obtaining the source

First install Jiri.

Next run:

$ jiri init
$ jiri import minimal https://fuchsia.googlesource.com/integration
$ jiri update

Third party

Third party projects should have their own subdirectory in ./third_party.