)]}'
{
  "commit": "4b9728bec157796478831972fc8d07306dd9dcde",
  "tree": "f91e989aa8a599c156338d09d64dbe152d42b220",
  "parents": [
    "478eebf831985d4c4aeb4c781e20b0d7ecce5baf"
  ],
  "author": {
    "name": "Simon Marchi",
    "email": "simon.marchi@polymtl.ca",
    "time": "Tue Jan 03 14:22:16 2023 -0500"
  },
  "committer": {
    "name": "Simon Marchi",
    "email": "simon.marchi@polymtl.ca",
    "time": "Wed Jan 04 11:19:50 2023 -0500"
  },
  "message": "gdb: use gdb_test_multiple in gdb_breakpoint\n\nWhen running the testsuite in a non-optimized build on a slow machine, I\nsometimes get:\n\n    UNTESTED: gdb.gdb/selftest.exp: Cannot set breakpoint at captured_main, skipping testcase.\n\ndo_self_tests, in lib/selftest-support.exp, uses `with_timeout_factor\n10`, to account for the fact that reading the debug info of the gdb\nbinary (especially in a non-optimized GDB) can take time.  But then it\nends up calling gdb_breakpoint, which uses gdb_expect with a hard-coded\ntimeout of 30 seconds.\n\nFix this by making gdb_breakpoint use gdb_test_multiple, which is a\ndesired change anyway for this kind of simple command / expected\noutput case.\n\nChange-Id: I9b06ce991cc584810d8cc231b2b4893980b8be75\nReviewed-By: Lancelot Six \u003clancelot.six@amd.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "135ace68d5ede9e47dd454db0dce3a42d446ba11",
      "old_mode": 33188,
      "old_path": "gdb/testsuite/lib/gdb.exp",
      "new_id": "ba16b2ab315984cf83defafd0836805ddd79c5f0",
      "new_mode": 33188,
      "new_path": "gdb/testsuite/lib/gdb.exp"
    }
  ]
}