[roll] Roll fuchsia [fdf] Reboot instead of mexec if node-removal timeout Make the driver manager fallback to hard rebooting when executing the mexec shutdown strategy if there are still nodes that haven't finished being removed. In such a scenario, the blocked nodes may be bound to driver instances that are holding onto DMA memory and mexec does not recover that memory. Only a hard reboot will clear the DMA memory. Add tests to verify that the shutdown manager performs a hard reboot if the system is configured to use the mexec shutdown strategy but the node-removal has timed out. Original-Original-Bug: 523366083 Test: driver-runner-tests TAG: agy CONV: 0a7e9cae-7d70-48a6-babc-eae6e8f1fe3f Original-Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1831736 Original-Original-Revision: 9b5626564d45525b9b16464608073146cd2bc84f GitOrigin-RevId: 828b4747c05ad2b37e822a43fa65a6b704178fe2 Change-Id: Ic6b731cc64bfc7b587fc565d79f6f305c7c2b8fe Reviewed-on: https://fuchsia-review.googlesource.com/c/integration/+/1857739 Cr-Commit-Position: refs/heads/main@{#203744}
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.