[roll] Roll fuchsia [component] component-manager records first and last 150 start/stop events in inspect As part of enabling escrow this will help indicate how frequently components are started in the field and debug problems when feedback is filed. I repurposed the `early_start_times` inspect node since miguelfrde@ mentioned it was an old experiment. fxbug.dev/104396 suggests people might be interested in component start times during boot, so I've preserved those data, effectively creating two lifetime inspect nodes: lifecycle: early: first 150 start/stop times late: last 150 start/stop times In terms of resource usage, let's say conservatively one event is 200 bytes in inspect, including monikers and string references. 300 events is 59 KiB so should not be that bad. Run-All-Tests: True Multiply: component_manager_status_tests Original-Bug: b/333078100 Original-Bug: b/332389972 Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1026700 Original-Revision: 20d8786211b8809ba390319beee7138e77dc5465 GitOrigin-RevId: 984ade07d4912134b1ec39ac28e1b4eab1e81846 Change-Id: Ife215571882811eb5b19b8f332df8e8b3b68a78c
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.