)]}'
{
  "commit": "940bb336cbce23f1780c449a7c72ca41e8d91fa5",
  "tree": "3147cb08f58261cb832a6051baf365665df1b481",
  "parents": [
    "d86dbbea8a81ab499cbf6969cee54a051817e025"
  ],
  "author": {
    "name": "Tom de Vries",
    "email": "tdevries@suse.de",
    "time": "Tue Sep 26 16:28:48 2023 +0200"
  },
  "committer": {
    "name": "Tom de Vries",
    "email": "tdevries@suse.de",
    "time": "Tue Sep 26 16:28:48 2023 +0200"
  },
  "message": "[gdb/testsuite] Fix gdb.server/ext-run.exp in container\n\nWhen running the gdb testsuite inside a container, I run into:\n...\n(gdb) gdb_expect_list pattern: /1 +root +[/a-z]*(init|systemd)/\nFAIL: gdb.server/ext-run.exp: get process list (pattern 2)\n...\nbecause there\u0027s no process with pid 1 and cmd init or systemd.\n\nIn the host system (where the test passes), I have:\n...\n$ ps -f 1\nUID        PID  PPID  C STIME TTY      STAT   TIME CMD\nroot         1     0  0 Sep25 ?        Ss     0:03 /usr/lib/systemd/systemd ...\n...\nbut in the container instead:\n...\nUID        PID  PPID  C STIME TTY      STAT   TIME CMD\nroot         1     0  0 11:45 pts/0    Ss     0:00 /bin/bash\n...\n\nFix this by also accepting bash as a valid cmd.\n\nTested on x86_64-linux.\n\nApproved-By: Tom Tromey \u003ctom@tromey.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "59ead666d7b8127110ba88296c82d8a5633ece14",
      "old_mode": 33188,
      "old_path": "gdb/testsuite/gdb.server/ext-run.exp",
      "new_id": "269158cd5b87226ff5b616ef40746bfe4bada57c",
      "new_mode": 33188,
      "new_path": "gdb/testsuite/gdb.server/ext-run.exp"
    }
  ]
}