[roll] Roll fuchsia [component_manager] CreateChild blocks on Discover action

fuchsia.sys2.Realm/CreateChild now waits on the Discover action before
it returns. This gives clients more predictable behavior: once
CreateChild returns, all the effects associated with the creation have
happened, such as the component's entry existing in the hub.

Original-Fixed: 75821
Multiply: hub_integration_test: 500

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/533561
Original-Revision: 31e2fcade6430b77555f4eaa654d8df94cf49c2b
GitOrigin-RevId: 5a20db916ce4d1b72026f50661f765cd056b379a
Change-Id: I438f4a76bb594268fe4a517a35d5c007047f0402
1 file changed
tree: e48283cd9a0969dcf57ffab61c757e7be5ba25a7
  1. garnet/
  2. infra/
  3. peridot/
  4. third_party/
  5. topaz/
  6. zircon/
  7. firmware
  8. flower
  9. jiri.lock
  10. minimal
  11. prebuilts
  12. README.md
  13. stem
  14. 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 via the IRC channel #fuchsia on Freenode.

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.