[roll] Roll fuchsia [gpt] enforce shutdown order, implement admin Make sure component manager sends the lifecycle stop request to fshost before anything in fs-collection, including the new gpt component. Until this change, the gpt component was getting shut down before the filesystems, causing a bunch of journal flushing issues. This also implements fuchsia.fs.Admin, so fshost can successfully call Shutdown on the gpt component. Original-Fixed: 391889311 Original-Bug: 391891190 Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1198692 Original-Revision: 8ced856758d9a135ff59c03d2059fd5585124ee5 GitOrigin-RevId: 4faf865d439297f6588845925644e805c32429f4 Change-Id: I3d6f38c47ccf702aafad18307d7d27e16fc2ed2c
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.