[roll] Roll fuchsia [metrics] Log reboot reason as Starnix Crash for the Session restarts The Fuchsia last reboot reason that the console ramoops file exposes was mismatched with the Android reboot reason when the Android was restarted due to a Session restart. A Starnix crash leads to a Session restart and also drives the Android running on top of it to restart abruptly. This sets the Android bootreason to be "kernel_panic". The Fuchsia reboot reason, on the other hand, wasn't changed by the occurrence of a Starnix crash as it doesn't cause the system reboot. So the Fuchsia reboot reason exposed was unrelated to the Session restart event. This changes the console ramoops file to expose 'Starnix Crash' as a reboot reason for these cases. Original-Bug: 489129965 Test: read back the ramoops file after causing a session restart Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1551540 Original-Revision: c5b735d7e12445c8dbb2f142ae490ab783d007e8 GitOrigin-RevId: 2138298cabc1107cf6847257d263f8e49aab9b0e Change-Id: I0fb64c890a87ff38b55be0f07aced6a452a889ce
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.