)]}'
{
  "commit": "4d559617cd9c0fe5c047bad610be9f6ebbbb19c9",
  "tree": "8ae2431cd32a8b3527e601937415cfbc6054abf1",
  "parents": [
    "f4ce8e532476a26ba18459cbd3622f50258969fe"
  ],
  "author": {
    "name": "David Benjamin",
    "email": "davidben@google.com",
    "time": "Wed May 18 14:31:51 2016 -0400"
  },
  "committer": {
    "name": "Adam Langley",
    "email": "agl@google.com",
    "time": "Wed May 18 18:59:38 2016 +0000"
  },
  "message": "Unflake Unclean-Shutdown-Alert on Windows.\n\nOn Windows, if we write to our socket and then close it, the peer sometimes\ndoesn\u0027t get all the data. This was working for our shimShutsDown tests because\nwe send close_notify in parallel with the peer and sendAlert(alertCloseNotify)\ndid not internally return an error.\n\nFor convenience, sendAlert returns a local error for non-close_notify alerts.\nSuppress that error to avoid the race condition. This makes it behave like the\nother shimShutsDown tests.\n\nChange-Id: Iad256e3ea5223285793991e2eba9c7d61f2e3ddf\nReviewed-on: https://boringssl-review.googlesource.com/7980\nReviewed-by: Adam Langley \u003cagl@google.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "36ca20221eaea37ea5c175d07c15abf9977dc838",
      "old_mode": 33188,
      "old_path": "ssl/test/runner/conn.go",
      "new_id": "3913995b8e299447cdf55d125fb30327be5d5168",
      "new_mode": 33188,
      "new_path": "ssl/test/runner/conn.go"
    }
  ]
}