)]}'
{
  "commit": "a3da2e7e550c4fe79128b5e532dbb90df4d4f418",
  "tree": "0d17df26d12917fe5ee6c4242b258c657615822d",
  "parents": [
    "4e08903f679f22be6d7ea6e33f21a9fc43210567"
  ],
  "author": {
    "name": "Bruno Larsen",
    "email": "blarsen@redhat.com",
    "time": "Tue Feb 21 17:10:31 2023 +0100"
  },
  "committer": {
    "name": "Bruno Larsen",
    "email": "blarsen@redhat.com",
    "time": "Mon Feb 27 10:52:23 2023 +0100"
  },
  "message": "gdb/testsuite: Improve testing of GDB\u0027s completion functions\n\nWhen looking at some failures of gdb.linespec/cp-completion-aliases.exp,\nI noticed that when a completion test will fail, it always fails with a\ntimeout.  This is because most completion tests use gdb_test_multiple\nand only add a check for the correct output.  This commit adds new\noptions for both, tab and command completion.\n\nFor command completion, the new option will check if the prompt was\nprinted, and fail in this case. This is enough to know that the test has\nfailed because the check comes after the PASS path. For tab completion,\nwe have to check if GDB outputted more than just the input line, because\nsometimes GDB would have printed a partial line before finishing with\nthe correct completion.\n\nApproved-By: Tom Tromey \u003ctom@tromey.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "bf9c5ad352c7594d2e8acac97fa4cf00274575a3",
      "old_mode": 33188,
      "old_path": "gdb/testsuite/lib/completion-support.exp",
      "new_id": "275f8874f15885d583ae207a27c224d79ebe657d",
      "new_mode": 33188,
      "new_path": "gdb/testsuite/lib/completion-support.exp"
    }
  ]
}