)]}'
{
  "commit": "488ed354c8514ba93286f8676a64b7841bb1fda4",
  "tree": "a59f09a2387fbfbb729c3a1382ac20ffb109670f",
  "parents": [
    "dd6c5a9217002033149a92bc48999370c451d025"
  ],
  "author": {
    "name": "Tom de Vries",
    "email": "tdevries@suse.de",
    "time": "Sat Oct 29 09:20:36 2022 +0200"
  },
  "committer": {
    "name": "Tom de Vries",
    "email": "tdevries@suse.de",
    "time": "Sat Oct 29 09:20:36 2022 +0200"
  },
  "message": "[gdb/testsuite] Remove REMOTE_PORTNUM in remote-stdio-gdbserver.exp\n\nThe usage for board remote-stdio-gdbserver.exp is advertised as:\n...\n # bash$ make check RUNTESTFLAGS\u003d\"--target_board\u003dremote-stdio-gdbserver \\\n #    REMOTE_USERNAME\u003d... REMOTE_HOSTNAME\u003d... REMOTE_PORTNUM\u003d... \\\n #    [REMOTE_TMPDIR\u003d${remote_dir}] [GDBSERVER\u003d${remote_gdbserver}]\"\n...\nbut when adding REMOTE_PORTNUM\u003d22, I run into:\n...\nRunning stop-reply-no-thread-multi.exp ...\nERROR: tcl error sourcing stop-reply-no-thread-multi.exp.\nERROR: couldn\u0027t execute \"/usr/bin/ssh -p22\": no such file or directory\n    while executing\n\"builtin_spawn {/usr/bin/ssh -p22} -l vries localhost {/usr/bin/gdbserver \\\n  --once localhost:2346 \\\n  /home/vries/gdb_versions/devel/build/gdb/testsuite/outp...\"\n...\n\nFix this by simply removing REMOTE_PORTNUM.\n\nTested on x86_64-linux.\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "101f1ee809846a41d3004bbd7276f5d4ba1309be",
      "old_mode": 33188,
      "old_path": "gdb/testsuite/boards/remote-stdio-gdbserver.exp",
      "new_id": "e1a2d0ed00746ac642793443c8595262088b1c13",
      "new_mode": 33188,
      "new_path": "gdb/testsuite/boards/remote-stdio-gdbserver.exp"
    }
  ]
}