)]}'
{
  "commit": "535394beb227d2a992fbe7a54bc3b69ef20c9ca2",
  "tree": "3aecb8432ff646b3de7d93e992bf32bfbeaa2a0d",
  "parents": [
    "62100f2546edfc85708dd30320a8b51d1f272e6b"
  ],
  "author": {
    "name": "David Gow",
    "email": "davidgow@google.com",
    "time": "Thu Jun 27 10:59:09 2019 -0700"
  },
  "committer": {
    "name": "David Gow",
    "email": "davidgow@google.com",
    "time": "Thu Jun 27 16:18:47 2019 -0700"
  },
  "message": "kunit_tool: Move log printing out of kunit_parser\n\nCurrently, kunit_parser will print a test log in parse_run_tests. This\nmeans that, in kunit_test, there is a lot of confusing output from the\nincluded test logs.\n\nThis change makes kunit_parser write its log to a string, which may then\noptinally be printed by its caller. In this case, we make the main\n\u0027kunit.py\u0027 print out the test log when running tests, but to not make\nkunit_test do so, as to not clutter the unittest output.\n\nIn doing this, the kunit_parser.TestResult type is changed to a class\n(with an additional \u0027pretty_log\u0027 function which writes to\nTestResult.log_lines), replacing the old namedtuple\nimplemenatation. There is also an additional\nTestResult.print_pretty_log() function to print this log.\n\nSigned-off-by: David Gow \u003cdavidgow@google.com\u003e\nChange-Id: Ib6c70f9749cf3daf513c150d472b58903aff0202\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "dc4d14da431afc162a7e16e95a712a845d8903e5",
      "old_mode": 33261,
      "old_path": "tools/testing/kunit/kunit.py",
      "new_id": "2536c745c681afe1cd16a54e63443f67930e53d9",
      "new_mode": 33261,
      "new_path": "tools/testing/kunit/kunit.py"
    },
    {
      "type": "modify",
      "old_id": "02b4abeaf1886473b72fa78f537856824fa39705",
      "old_mode": 33188,
      "old_path": "tools/testing/kunit/kunit_parser.py",
      "new_id": "4d65e0a807285ce1ba926a3a68cbc0edb105cf35",
      "new_mode": 33188,
      "new_path": "tools/testing/kunit/kunit_parser.py"
    }
  ]
}
