)]}'
{
  "commit": "0859ce6f6b25ddeb6ab6529b7621b5b311f3a5a6",
  "tree": "2c6425df8158005826bd445bf1ae32d3bed4f61f",
  "parents": [
    "4d80a39016b66978e9343447ee10c3cec06a6820"
  ],
  "author": {
    "name": "Tony Gentilcore",
    "email": "tonyg@chromium.org",
    "time": "Mon Jan 11 09:18:35 2016 -0800"
  },
  "committer": {
    "name": "Tony Gentilcore",
    "email": "tonyg@chromium.org",
    "time": "Mon Jan 11 09:18:35 2016 -0800"
  },
  "message": "Fix dart apptest flake on android.\n\nThere\u0027s a good discussion of this issue in dart-lang/test#333. In short,\ntearDownAll is guaranteed to be called after all tests run. However,\napptest.dart explicitly calls close() in tearDownAll, which closes the shell.\n\nThis close races against the test framework getting around to outputting\n\"All tests pass!\". So this patch works around it by instead looking for the\nmessage about tearDownAll running with no previously failed tests.\n\nBUG\u003dFixes #394\nR\u003djohnmccutchan@google.com, zra@google.com\n\nReview URL: https://codereview.chromium.org/1569213004 .\n\nCr-Mirrored-From: https://github.com/domokit/mojo\nCr-Mirrored-Commit: 66269650afe77c016cd33903e5d02ea05d879660\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "fe6131f8ac085a6dacf6d38e60a52632d69cfb23",
      "old_mode": 33188,
      "old_path": "devtoolslib/apptest_dart.py",
      "new_id": "3c7a685b644b83e3ce7bf39f59d1780ddc375330",
      "new_mode": 33188,
      "new_path": "devtoolslib/apptest_dart.py"
    }
  ]
}