)]}'
{
  "commit": "07fbeaea1d7759e3c03def5ccc031a70f4218ae6",
  "tree": "3aade8cfa1332870cfa759b433e0a859071b985f",
  "parents": [
    "c781f45de27afe3a90dcadb5075dc90df8105d80"
  ],
  "author": {
    "name": "laszlocsomor",
    "email": "laszlocsomor@google.com",
    "time": "Mon Apr 10 14:32:07 2017 +0000"
  },
  "committer": {
    "name": "Jakob Buchgraber",
    "email": "buchgr@google.com",
    "time": "Tue Apr 11 10:49:42 2017 +0200"
  },
  "message": "cc_configure: stricter error checks in _execute\n\nAdd stricter error checks in hopes of catching\noccasional CI flakiness where the stdout of a\ncommand seems to get lost.\n\nIt\u0027s now an error if the command returns a\nnon-zero exit code (or a zero one if it\u0027s expected\nto fail) or if its stdout is empty. Previously we\nonly checked if stderr was empty to consider the\naction successful.\n\nSee https://github.com/bazelbuild/bazel/issues/2675\n\nRELNOTES: none\nPiperOrigin-RevId: 152685220\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "73653e9d1021ce3f6ef9a4b57f253862d0ce652e",
      "old_mode": 33188,
      "old_path": "tools/cpp/cc_configure.bzl",
      "new_id": "fd7edd0b54e654fc0ad1accfd6b423d11a6880e6",
      "new_mode": 33188,
      "new_path": "tools/cpp/cc_configure.bzl"
    }
  ]
}