)]}'
{
  "commit": "6057647ed7f2d00000a783218d992d4cf7433aee",
  "tree": "b5199d96d06effd098439ece51113140c1d0b1e5",
  "parents": [
    "31162eba03ef4c6b3ae8a52540b1ea85b455ce57"
  ],
  "author": {
    "name": "Geoffrey Martin-Noble",
    "email": "gcmn@google.com",
    "time": "Mon Nov 21 18:22:41 2022 -0800"
  },
  "committer": {
    "name": "GitHub",
    "email": "noreply@github.com",
    "time": "Mon Nov 21 18:22:41 2022 -0800"
  },
  "message": "Shut down runner VM if startup fails (#11250)\n\nI was planning to do this as health check, which integrates with the\r\nactual MIG infrastructure, but that has ended up being a laborious\r\nprocess due to Google security rules and I still haven\u0027t gotten it to\r\nwork. In the meantime, we\u0027ve been having frequent issues with server\r\nerrors from the GitHub actions control plane, which mean that the\r\nrunners are never registered and the instances just sit around\r\ncounting as \"running\" according to the autoscaler.\r\n\r\nThis is a really simple method to just shut down the runners if setup\r\nfails. We should also add retries and stuff, but this works for now and\r\nshould hopefully avoid us ending up with half our instance pool just\r\nsitting idle.\r\n\r\nTested:\r\nI added a non-deterministic failure in the setup script (see reverted\r\ncommit) and confirmed that some of the instances initially shut down,\r\nbut eventually all came online as runners.\r\n\r\nskip-ci: Runner startup configuration not tested by CI.",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "286ad179f1aa05a9b9b03af09260014a5de4d183",
      "old_mode": 33261,
      "old_path": "build_tools/github_actions/runner/config/setup.sh",
      "new_id": "cd8920a31fe9bc1f22cd100c83f53d60da78dfc7",
      "new_mode": 33261,
      "new_path": "build_tools/github_actions/runner/config/setup.sh"
    }
  ]
}