)]}'
{
  "commit": "6f07a038d7bd94de65f9d59cb9788a8c0b871176",
  "tree": "e61756859a2855a781788260373299863f1792af",
  "parents": [
    "9826b9763919cba82b99c912484f49c45696b259"
  ],
  "author": {
    "name": "Nick Eaton",
    "email": "nickeaton@fuchsia.infra.roller.google.com",
    "time": "Wed Sep 30 14:51:24 2026 -0700"
  },
  "committer": {
    "name": "Copybara Service",
    "email": "copybara-worker@google.com",
    "time": "Wed Sep 30 14:51:24 2026 -0700"
  },
  "message": "[roll] Roll fuchsia [fdf] Reboot instead of mexec if node-removal timeout\n\nMake the driver manager fallback to hard rebooting when executing the\nmexec shutdown strategy if there are still nodes that haven\u0027t finished\nbeing removed. In such a scenario, the blocked nodes may be bound to\ndriver instances that are holding onto DMA memory and mexec does not\nrecover that memory. Only a hard reboot will clear the DMA memory.\n\nAdd tests to verify that the shutdown manager performs a hard reboot if\nthe system is configured to use the mexec shutdown strategy but the\nnode-removal has timed out.\n\nOriginal-Original-Bug: 523366083\nTest: driver-runner-tests\nTAG: agy\nCONV: 0a7e9cae-7d70-48a6-babc-eae6e8f1fe3f\nOriginal-Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1831736\nOriginal-Original-Revision: 9b5626564d45525b9b16464608073146cd2bc84f\nGitOrigin-RevId: 828b4747c05ad2b37e822a43fa65a6b704178fe2\nChange-Id: Ic6b731cc64bfc7b587fc565d79f6f305c7c2b8fe\nReviewed-on: https://fuchsia-review.googlesource.com/c/integration/+/1857739\nCr-Commit-Position: refs/heads/main@{#203744}\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "ca86a1f0efb401e0dcadab8246e4e82452c0a351",
      "old_mode": 33188,
      "old_path": "stem",
      "new_id": "4e9a9d129ce01592efb3014bb65db3f83a481936",
      "new_mode": 33188,
      "new_path": "stem"
    }
  ]
}
