[roll] Roll fuchsia [component_manager] Remove hub workarounds for destroy out of order

With fxbug.dev/100652, a destroy event should always follow all other
events on the component instance. Undo the workarounds applied in
fxrev.dev/633767 and fxrev.dev/635825.

Original-Bug: 89503
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/692097
Original-Revision: e54aeb397f60fc0fb984cc9c3ee4ed5172663301
GitOrigin-RevId: 5a5fb703b0b0da0467521502af882b349f00a6c9
Change-Id: I1d3ca09633d15915cc50d56d59bba6ba8b071f7c
1 file changed
tree: 9ac54653765aee67d3f77c9fa961cc4e36e80111
  1. infra/
  2. third_party/
  3. cts
  4. firmware
  5. flower
  6. jiri.lock
  7. minimal
  8. prebuilts
  9. README.md
  10. stem
  11. test_durations
  12. toolchain
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.