)]}'
{
  "commit": "16a4de2bb031e79c1606775805db1dabbf433b7b",
  "tree": "ea2e8c4b1cdba000d05928eb036b34ec40bf1c03",
  "parents": [
    "8841d123a5d378068d6d7666fe95abbbc8b4cba6"
  ],
  "author": {
    "name": "K. Moon",
    "email": "kmoon@chromium.org",
    "time": "Sat Oct 22 01:50:53 2022 +0000"
  },
  "committer": {
    "name": "Pdfium LUCI CQ",
    "email": "pdfium-scoped@luci-project-accounts.iam.gserviceaccount.com",
    "time": "Sat Oct 22 01:50:53 2022 +0000"
  },
  "message": "Report test_runner.py test case output to ResultDB\n\nRecords test output from individual test_runner.py test case failures,\nthen reports it to ResultDB.\n\nNote that any output from commands directly spawned by test_runner.py\nwill now be intercepted, and only reported after the test completes.\n(This is not yet true for the image differ, however.)\n\nThis change refactors the test case-running logic into a new, per-case\n_TestCaseRunner class. This reduces the need to pass state through to\nindividual test case steps.\n\nAlso cleans up the stale TODO from crbug.com/pdfium/1657, and drops\nKeyboardInterruptError as irrelevant in multiprocessing mode.\n\nBug: pdfium:1657, pdfium:1916\nChange-Id: I6b030d16d5ffc32ef0b9488c699decc54d771110\nReviewed-on: https://pdfium-review.googlesource.com/c/pdfium/+/99951\nReviewed-by: Lei Zhang \u003cthestig@chromium.org\u003e\nReviewed-by: Tom Sepez \u003ctsepez@chromium.org\u003e\nCommit-Queue: K. Moon \u003ckmoon@chromium.org\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "24122469152a049c5ca61afa1e6bca38dd0cff31",
      "old_mode": 33188,
      "old_path": "testing/tools/test_runner.py",
      "new_id": "44a3f3dea5f9ae0f89b1b57135a448c2a1b78ec1",
      "new_mode": 33188,
      "new_path": "testing/tools/test_runner.py"
    }
  ]
}