)]}'
{
  "commit": "c3c6ea92a02cb6bba18175c713cdedec18309d28",
  "tree": "0234a4757bbfbf6bda04fb6678faf8be9b7fbd22",
  "parents": [
    "8edf302884c0618fdaea02629d330b9c259ee62e"
  ],
  "author": {
    "name": "Charlie Mooney",
    "email": "charliemooney@chromium.org",
    "time": "Thu Sep 10 17:23:40 2015"
  },
  "committer": {
    "name": "chrome-bot",
    "email": "chrome-bot@chromium.org",
    "time": "Fri Sep 11 20:51:03 2015"
  },
  "message": "Initialize TID to dummy value correctly\n\nPreviously the code in the quickstep latency measurement script\nassumes a dummy value of -1 was put into the current TID, but that\nwas not the case.  It turns out it was actually a 0, which is a\nperfectly legal value.  This didn\u0027t cause problems because usually\nthe first event immediately overwrites that value.  I\u0027ve been\nusing a device where that is not the case (from a new vendor) and\nthis script now fails.\n\nThis CL simply changes the value to be initialized to -1 like it\nwas supposed to, and it seems to fix the problem.\n\nBUG\u003dnone\nTEST\u003dmanually tested\n\nChange-Id: I87790b2a0dfac39ffdfba22777deb1bdc6d7e3a6\nSigned-off-by: Charlie Mooney \u003ccharliemooney@chromium.org\u003e\nReviewed-on: https://chromium-review.googlesource.com/298870\nReviewed-by: Shyh-In Hwang \u003cjosephsih@chromium.org\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "e1362c272fc40e09f7245ac63ae18b135b3f8897",
      "old_mode": 33188,
      "old_path": "quickstep/latency_measurement.py",
      "new_id": "c8af55d978ce46b72bcaa3d7c90398303f9a7dbc",
      "new_mode": 33188,
      "new_path": "quickstep/latency_measurement.py"
    }
  ]
}