)]}'
{
  "commit": "d0512c4a9ef8acd6a42b21680421023925d11ac2",
  "tree": "10acd9ea5f0ad0c3ad4c4d153a2f919cd56834e3",
  "parents": [
    "14db507c284a936dc14559f095a4629d5c52f5d8"
  ],
  "author": {
    "name": "Laszlo Csomor",
    "email": "laszlocsomor@google.com",
    "time": "Mon Mar 20 16:10:39 2017 +0000"
  },
  "committer": {
    "name": "Yue Gan",
    "email": "yueg@google.com",
    "time": "Tue Mar 21 12:49:00 2017 +0000"
  },
  "message": "Bazel client, Windows: fix server kill failures\n\nFix the (spurious) error messages about the Bazel\nclient\u0027s failure to kill the server process, with\n\"Access Denied\" errors.\n\nThis was caused by our attempt to kill the server\nprocess twice, and the error was coming from the\nsecond attempt.\n\nThe culprit was an unimplemented\nVerifyServerProcess method (which ensures that the\nPID read from the server.pid.txt indeed refers to\na running Bazel server) which always returned\nfalse, to avoid accidentally killing an unrelated\nprocess that got the same PID as the last alive\nBazel server.\n\nThe new code follows the same logic as the Linux\nversion of Bazel, namely storing the process\u0027\nstart time in a file next to the PID file, and\nchecking that the process with said PID was\nindeed started at the time we read from the file.\n\nThis change also fixes a problem that the now\nworking VerifyServerProcess uncovered: we need to\nwait for the previous Bazel server to properly\nshut down before we can open the new jvm.out log\nfile.\n\nFixes https://github.com/bazelbuild/bazel/issues/2684\n\n--\nPiperOrigin-RevId: 150632429\nMOS_MIGRATED_REVID\u003d150632429\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "c721ba919c401149a13a097c3e36b19e315414a8",
      "old_mode": 33188,
      "old_path": "src/main/cpp/blaze_util_windows.cc",
      "new_id": "6f5ffb23482a1cbaf09f6229b3942635e9342364",
      "new_mode": 33188,
      "new_path": "src/main/cpp/blaze_util_windows.cc"
    }
  ]
}