)]}'
{
  "commit": "14b5cb047e87f5aa40a33839c3f0e32a1ee3570e",
  "tree": "2b8dea1d41af38da4041353dc3e76a891e5c343e",
  "parents": [
    "a95b752dc6ee807e74bc3efd1b8985e69a2d7152"
  ],
  "author": {
    "name": "Chris Bracken",
    "email": "chris@bracken.jp",
    "time": "Mon Nov 20 17:37:14 2017 -0800"
  },
  "committer": {
    "name": "GitHub",
    "email": "noreply@github.com",
    "time": "Mon Nov 20 17:37:14 2017 -0800"
  },
  "message": "Use duration not threadDuration for frame duration (#13117)\n\n1. We want to measure wall-clock duration for the benchmarks, as opposed\r\n   to thread duration (e.g., waiting on a mutex should accrue time) and\r\n   \u0027dur\u0027 is the metric to use for that.\r\n\r\n2. On Darwin-based systems (macOS and iOS) \u0027tdur\u0027 is the result of a\r\n   mach syscall lookup to thread_info. This call returns unreliable data\r\n   on iOS. Chromium, for example, disables thread time support entirely\r\n   for iOS.",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "bc1e3c62ba5abcde29ac0e2ad131c63a60e937ef",
      "old_mode": 33188,
      "old_path": "packages/flutter_driver/lib/src/timeline_summary.dart",
      "new_id": "99a70c68df8195a8af4d606f74ffc17be3a87258",
      "new_mode": 33188,
      "new_path": "packages/flutter_driver/lib/src/timeline_summary.dart"
    },
    {
      "type": "modify",
      "old_id": "9fea04efb6b3e7b0a6ffab1baf57293d249523c1",
      "old_mode": 33188,
      "old_path": "packages/flutter_driver/test/src/timeline_summary_test.dart",
      "new_id": "d96887c67cfafc3417d5d660e16bf9ba0b03b0d0",
      "new_mode": 33188,
      "new_path": "packages/flutter_driver/test/src/timeline_summary_test.dart"
    }
  ]
}