)]}'
{
  "commit": "c09325a5a67c613ba97057f7132e98fd99508666",
  "tree": "2c709d362834a0a488bd4202d34cd69bdaa4d4f0",
  "parents": [
    "ef6302a6d160eaa67f9f5eafbe4c8bee20201258"
  ],
  "author": {
    "name": "Simon Marchi",
    "email": "simon.marchi@efficios.com",
    "time": "Mon Aug 25 11:44:22 2025 -0400"
  },
  "committer": {
    "name": "Simon Marchi",
    "email": "simon.marchi@efficios.com",
    "time": "Thu Aug 28 13:36:30 2025 -0400"
  },
  "message": "gdb/testsuite: use gdb_test_no_output when dumping in gdb.base/dump.exp\n\nI don\u0027t know if this is true on all platforms, but from what I can see\non Linux, the dump commands don\u0027t output anything.  Use\ngdb_test_no_output, which should be a bit more robust than checking for\nsome specific error patterns.\n\nChange-Id: Idc82298c4752ba7808659dfea2f8324c8a97052d\nApproved-By: Tom Tromey \u003ctom@tromey.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "a55e5b060db75af49f99c43f6438412c71b35d45",
      "old_mode": 33188,
      "old_path": "gdb/testsuite/gdb.base/dump.exp",
      "new_id": "7c84056dfa69cf2b78b6892736f6f51cadc9e8c7",
      "new_mode": 33188,
      "new_path": "gdb/testsuite/gdb.base/dump.exp"
    }
  ]
}