)]}'
{
  "commit": "a4c81e4401eefcc870e429b25dc25a42cef8bd98",
  "tree": "7d7b1dec69021a2427b7627a8f7cde80e87dba0b",
  "parents": [
    "c664ebe3c0dc4c0b7d8f71db4df6d892635977b8"
  ],
  "author": {
    "name": "Charlie Mooney",
    "email": "charliemooney@chromium.org",
    "time": "Fri Jul 10 21:42:05 2015"
  },
  "committer": {
    "name": "ChromeOS Commit Bot",
    "email": "chromeos-commit-bot@chromium.org",
    "time": "Mon Jul 13 18:43:55 2015"
  },
  "message": "Sort noise test results by frequency, not the order they were run\n\nPreviously, all the test results were put into the html report that\nthe touch FW test generated, simply in the order they were run.  This\nworked fine until recently when we made it run the noise test in a\nrandomized order (to improve the validity of the test).  Now the\nresults are also in a random order, which makes it hard to read since\nerrors tend to happen in bands of frequencies.  eg: a user might\nwant to see the details of all the tests around 200khz, but they\u0027re\nscattered through out the report now.\n\nThis CL adds in some logic to filter out the noise tests and sort\nthem by the frequency of the noise being tested before rending the\nreport.  Non-noise tests are left un-touched, since they are already\ngrouped by the type of gesture, which is what we want.\n\nBUG\u003dchromium:509074\nTEST\u003dmanually tested, the reports look to be in a sane, useful order.\n\nChange-Id: Ib12917e3ab2b64318a0fbde7793c533cfddcf63c\nSigned-off-by: Charlie Mooney \u003ccharliemooney@chromium.org\u003e\nReviewed-on: https://chromium-review.googlesource.com/284866\nReviewed-by: Amirhossein Simjour \u003casimjour@chromium.org\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "2c7ebfcad13a6f4262e68ea19ba4fe3bc27b1b5e",
      "old_mode": 33188,
      "old_path": "report/report.py",
      "new_id": "dca2d4cc1d79d1ec85bb761de6a733a5a569c742",
      "new_mode": 33188,
      "new_path": "report/report.py"
    }
  ]
}