)]}'
{
  "commit": "6b48efac7b3b229c17cff55e5cfd9f9a0aea9b70",
  "tree": "483c3ddd45b937a78b8500b5188a156e827d4b83",
  "parents": [
    "04b3213d43492b6c9e0434d8e2a4530a9938f958"
  ],
  "author": {
    "name": "Dan McArdle",
    "email": "dmcardle@google.com",
    "time": "Thu Mar 11 18:25:49 2021 -0500"
  },
  "committer": {
    "name": "CQ bot account: commit-bot@chromium.org",
    "email": "commit-bot@chromium.org",
    "time": "Fri Mar 12 16:38:54 2021 +0000"
  },
  "message": "Add -rr-record flag to runner.go.\n\nThis flag causes the runner to execute the shim with the RR debugger.\nSee https://rr-project.org/.\n\nUnlike typical debuggers, the RR workflow is to first record a session\nand then replay it. The user cannot interact with the debugger while\nrecording and they replay the session multiple times. For these reasons,\nI\u0027ve opted not to launch xterm like -gdb and -lldb do.\n\nThe other difference is that -rr-record restricts the runner to exactly\none test. Otherwise, it\u0027s too easy to accumulate a bunch of unwanted\nrecordings. Also, `rr replay` uses the most recent recording by default,\nso it\u0027s not very useful for runner to record multiple tests.\n\nChange-Id: I2d29d64df5c4c832e50833325db3500ec2698e76\nReviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/46144\nCommit-Queue: David Benjamin \u003cdavidben@google.com\u003e\nReviewed-by: David Benjamin \u003cdavidben@google.com\u003e\nReviewed-by: Adam Langley \u003cagl@google.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "9af820ecef1bade7ec0ca2c474440d1417a48d80",
      "old_mode": 33188,
      "old_path": "ssl/test/runner/runner.go",
      "new_id": "cc0fd06c2f5d80bcbf8c62cbd6a76a6c0ad88bfb",
      "new_mode": 33188,
      "new_path": "ssl/test/runner/runner.go"
    }
  ]
}