)]}'
{
  "commit": "7afffa6447c83352b95ff91968ab2dc9ad64d38c",
  "tree": "49ae0527c6bcf0850e6ec021d03987b666489af0",
  "parents": [
    "f10d8feca0bc5cf4d707f485bb35ecefa9e97560"
  ],
  "author": {
    "name": "Sean Dague",
    "email": "sean.dague@samsung.com",
    "time": "Sat Mar 15 13:50:36 2014 -0400"
  },
  "committer": {
    "name": "Sean Dague",
    "email": "sean.dague@samsung.com",
    "time": "Sat Mar 15 13:50:36 2014 -0400"
  },
  "message": "change the order of the print/flush\n\nIt seems that we get a different behavior whether stdout is closed\nin the parent process or not when it comes to buffering. If it\u0027s\nclosed we don\u0027t get the last line flushed out to the file, if it\u0027s\nnot closed we do. This was seen in the trove pg fail.\n\nA complete shot in the dark, but I\u0027d like to see if this is fixed\nwith being explicit with printing to the log before stdout.\n\nChange-Id: Ie37299dbc88d549d34d85731e571a5b7ef181311\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "09e9eec803e03877b3f4971465f8910cbcbf4285",
      "old_mode": 33261,
      "old_path": "stack.sh",
      "new_id": "7fa4d37b07ee52ba0630fa957d6a4d07d9e7c0dc",
      "new_mode": 33261,
      "new_path": "stack.sh"
    }
  ]
}