[roll] Roll fuchsia [netemul] Wait for destroyed event ...rather than the stopped event to determine that the test realm has been shutdown. Because orderly shutdown happens in reverse dependency order, there is no guarantee that the root of a realm will be stopped before its children. However, there is a guarantee that a component will only be destroyed once it and all its descendants have been stopped, so once we observe the destroyed event for the test root, we are guaranteed the entire test realm has completed shutdown. Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/666703 Original-Revision: d994d4eb776a4284ef06a61fcdd45db6f8eecc0f GitOrigin-RevId: 9eba4e4e21b8d9c81460a5edd3ec43fb1fc0133e Change-Id: I6c74ca49864051a6569c2e4079bc59d6946103ef
This repository contains Fuchsia's Global Integration manifest files.
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.
First install Jiri.
Next run:
$ jiri init $ jiri import minimal https://fuchsia.googlesource.com/integration $ jiri update
Third party projects should have their own subdirectory in ./third_party.