)]}'
{
  "commit": "dc4315fb7c4ef3075d85152b0746df697e2aa26e",
  "tree": "b5c713b9fc5cbaaa8667d6e48c2a323bf97a6c08",
  "parents": [
    "067e12b39086ea4333d687e253b23e0d3d27f5d3"
  ],
  "author": {
    "name": "Vikram Gara",
    "email": "vikramgara@google.com",
    "time": "Thu Aug 20 00:46:32 2026 +0000"
  },
  "committer": {
    "name": "Vikram Gara",
    "email": "vikramgara@google.com",
    "time": "Wed Aug 19 19:59:57 2026 -0700"
  },
  "message": "Server 3.0: emmc-wait: Increase systemd timeout to match script\n\nCommit adef9d0f3aca increased the timeout in `wait_emmc_available.sh`\nto 900 seconds (15 minutes). However, the systemd unit `emmc-wait.service`\nwas left at its previous `TimeoutStartSec\u003d330s`, causing systemd to\nprematurely terminate the service before the script could finish waiting.\n\nThis change bumps `TimeoutStartSec` to 930 seconds (15.5 minutes),\nsynchronizing the service with the script and providing a 30-second\nbuffer so the script can gracefully timeout and log errors instead of\nbeing abruptly SIGTERM-ed by systemd.\n\nPlatforms-Affected: Server 3.0 platforms.\n\nfusion2: n/a\n\nTested: Bitbake builds\nGoogle-Bug-Id: 549235198\nChange-Id: I6efca51cf48e8c7de098bee6feadbdba66f45d71\nSigned-off-by: Vikram Gara \u003cvikramgara@google.com\u003e\n(cherry picked from commit 26f6de6c9e9a36cc2386f185d2ba0e7a4d6107ad)\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "e79ceb7937ce19d4af9b2774258c397684a8134f",
      "old_mode": 33188,
      "old_path": "recipes-google/gbmc-sysinit/server3/emmc-wait.service",
      "new_id": "d7dfdc04a047327e77a25a70ec586ec78e9c9e11",
      "new_mode": 33188,
      "new_path": "recipes-google/gbmc-sysinit/server3/emmc-wait.service"
    }
  ]
}