)]}'
{
  "commit": "58ce4199db5f24ca0becdc5709b71bc2d3561818",
  "tree": "e257dc863b8c66343069397821ccedc838d25246",
  "parents": [
    "d0b0a5e0f059d106f92b0d221d4739635b8a458c"
  ],
  "author": {
    "name": "Dodam Kim",
    "email": "dodam@fuchsia.infra.roller.google.com",
    "time": "Thu Apr 09 01:10:15 2026 -0700"
  },
  "committer": {
    "name": "Copybara-Service",
    "email": "copybara-worker@google.com",
    "time": "Thu Apr 09 01:13:12 2026 -0700"
  },
  "message": "[roll] Roll fuchsia [metrics] Log reboot reason as Starnix Crash for the Session restarts\n\nThe Fuchsia last reboot reason that the console ramoops file exposes was\nmismatched with the Android reboot reason when the Android was restarted\ndue to a Session restart.\nA Starnix crash leads to a Session restart and also drives the Android\nrunning on top of it to restart abruptly. This sets the Android\nbootreason to be \"kernel_panic\".\nThe Fuchsia reboot reason, on the other hand, wasn\u0027t changed by the\noccurrence of a Starnix crash as it doesn\u0027t cause the system reboot. So\nthe Fuchsia reboot reason exposed was unrelated to the Session restart\nevent.\nThis changes the console ramoops file to expose \u0027Starnix Crash\u0027 as a\nreboot reason for these cases.\n\nOriginal-Bug: 489129965\nTest: read back the ramoops file after causing a session restart\nOriginal-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1551540\nOriginal-Revision: c5b735d7e12445c8dbb2f142ae490ab783d007e8\nGitOrigin-RevId: 2138298cabc1107cf6847257d263f8e49aab9b0e\nChange-Id: I0fb64c890a87ff38b55be0f07aced6a452a889ce\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "4edb160efc2e9dacf61606ccb9e0608c31bed600",
      "old_mode": 33188,
      "old_path": "stem",
      "new_id": "1a249c5fa00ee92790dd8dc2066f13cf50660014",
      "new_mode": 33188,
      "new_path": "stem"
    }
  ]
}