)]}'
{
  "commit": "28d6979b7ec97546b78594925d49fa1071b28f73",
  "tree": "b382b3d619c706c007a13d0f757a2feb4eec7417",
  "parents": [
    "24e36099cee9c854e849844248db3c415a2add5d"
  ],
  "author": {
    "name": "David Benjamin",
    "email": "davidben@google.com",
    "time": "Sun Sep 03 13:18:48 2017 -0400"
  },
  "committer": {
    "name": "CQ bot account: commit-bot@chromium.org",
    "email": "commit-bot@chromium.org",
    "time": "Tue Sep 05 17:24:15 2017 +0000"
  },
  "message": "Print errors better in FileTestGTest.\n\nRather than clear them, even on failure, detect if an individual test\nfailed and dump the error queue there. We already do this at the GTest\nlevel in ErrorTestEventListener, but that is too coarse-grained for the\nfile tests.\n\nChange-Id: I3437626dcf3ec43f6fddd98153b0af73dbdcce84\nReviewed-on: https://boringssl-review.googlesource.com/19966\nReviewed-by: Steven Valdez \u003csvaldez@google.com\u003e\nReviewed-by: David Benjamin \u003cdavidben@google.com\u003e\nCommit-Queue: David Benjamin \u003cdavidben@google.com\u003e\nCQ-Verified: CQ bot account: commit-bot@chromium.org \u003ccommit-bot@chromium.org\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "1341b774aad0ac70f7bdf7207a57fd1e9d797760",
      "old_mode": 33188,
      "old_path": "crypto/evp/evp_test.cc",
      "new_id": "3bcdbd67eed1b18b26a0e8a6e26faba986ebdd16",
      "new_mode": 33188,
      "new_path": "crypto/evp/evp_test.cc"
    },
    {
      "type": "modify",
      "old_id": "cffacb35a0cbdd8b79c0df3d51f77ea8248b22d9",
      "old_mode": 33188,
      "old_path": "crypto/test/file_test_gtest.cc",
      "new_id": "bfa8d27d546066aafe3bfb8f4e83eb4ad857b923",
      "new_mode": 33188,
      "new_path": "crypto/test/file_test_gtest.cc"
    }
  ]
}