)]}'
{
  "commit": "9afa3393acf70d6d087e92857bc074259516e704",
  "tree": "65884f2363aad4219070d52525ad87a94211b25b",
  "parents": [
    "aead7cbe007b58179a17e6a78e51714a60869a5b"
  ],
  "author": {
    "name": "Karl Wiberg",
    "email": "kwiberg@google.com",
    "time": "Mon May 18 14:30:58 2015 +0200"
  },
  "committer": {
    "name": "Karl Wiberg",
    "email": "kwiberg@google.com",
    "time": "Mon May 18 14:30:58 2015 +0200"
  },
  "message": "Speed up tests by running the biggest ones first\n\nTowards the end of a test run, there\u0027s typically a period when only\none or a few cores are busy with the last of the tests---the ones that\ntake a very long time. By sorting the tests according to their\nexpected runtime and starting the longest-running ones first, we\nminimize this effect.\n\nThis patch records the runtime in ~/.gtest-parallel-times once all\ntests have finished; on subsequent runs, this data is used to start\nthe longest-running tests first. Speedup varies depending on which\ntests are run, but the usual seems to be about 10%, and I haven\u0027t\nobserved a slowdown for any set of tests (though admittedly, my sample\nis very modest).\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "71c0ed641886db7c48eaa3c590bba5a83c5cb6d2",
      "old_mode": 33261,
      "old_path": "gtest-parallel",
      "new_id": "58d2a67cc7d12e0cb907f7c9b33dc657fc5b37de",
      "new_mode": 33261,
      "new_path": "gtest-parallel"
    }
  ]
}