[roll] Roll fuchsia [component_manager] Re-enable tracing Re-enable tracing in component manager when general tracing is turned on. This was previously gated by a special option which was never set in practice. This includes fixing a deadlock (which is why tracing was disabled in the first place): component manager no longer waits for trace provider initialization to complete, since that involves component lifecycle and routing operations that are re-entrant to component manager and can create a deadlock if the reentry lands on the same thread. Tested: Locally adjusted component_manager thread pool size to 1 and verified boot deadlock no longer exists. Original-Original-Bug: 458746554 Original-Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1629628 Original-Original-Revision: 113bca810041f6624eb98df7dc91163c87efd29f GitOrigin-RevId: f5ee99ac13419cd5a5f4362059ac3c85c9b37bf1 Change-Id: I17d6eae33c575695377b126a88e961c3b0bd674e Reviewed-on: https://fuchsia-review.googlesource.com/c/integration/+/1653337 Cr-Commit-Position: refs/heads/main@{#194689}
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.