[roll] Roll fuchsia [component_manager] Remove StartComponentTree Event Stream When component manager was in debug mode, a special event stream called "StartComponentTree" was created above the root. This event stream subscribed to synchronous Resolved events. Doing so blocked the root component from being resolved, allowing a test to subscribe to events before starting up the component tree. There is a better way to do this now. If component manager is in debug mode, it will not bind to the root component automatically. To start the component tree, use the LifecycleController protocol in the hub to bind to the root. OpaqueTest now uses this technique instead. Original-Fixed: 52929 Multiply: component_manager_tests Multiply: elf_runner_lifecycle_test Multiply: events_integration_test Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/653164 Original-Revision: ab4bd84d10d2cafbeaa80d5d0cad358a878778eb GitOrigin-RevId: 66497f1eca5c9402fd9ac7e66340baa09841344d Change-Id: I191826e94789861fa584c80e0b41ca08b6bd70b4
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.