[roll] Roll fuchsia [component_manager] traces for routing and lifecycle Now that https://fxrev.dev/1629628 has landed, add some trace spans to component manager to measure lifecycle state and routing times. For example, this can help us understand system boot times by revealing how much time is spent doing component bringup and capability routing. Note: no performance tests enable the `component_manager` trace category yet, but we may do that in a followup. This is only a starting point and not close to exhaustive, we could add more trace events in the future. Original-Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1630120 Original-Original-Revision: d170feea39cf76317cb8d4c07d8004730a1ffb65 GitOrigin-RevId: de638793ec83cc255dfa1123cebeac4e018ad319 Change-Id: I6b377dd31c1572ae2a1495af4634b98cfc831fbb Reviewed-on: https://fuchsia-review.googlesource.com/c/integration/+/1673014 Cr-Commit-Position: refs/heads/main@{#195294}
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 in one of the communication channels documented at get involved.
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.