)]}'
{
  "commit": "35da8c6140344db53eff53189abffd8cb0bec2bc",
  "tree": "8a0c66df89fb2640eaa0a335afdd2922072b3ef4",
  "parents": [
    "5612b5d21e41796c9d6fb024c4bbf70719153373"
  ],
  "author": {
    "name": "Tom de Vries",
    "email": "tdevries@suse.de",
    "time": "Wed Oct 27 18:57:15 2021 +0200"
  },
  "committer": {
    "name": "Tom de Vries",
    "email": "tdevries@suse.de",
    "time": "Wed Oct 27 18:57:15 2021 +0200"
  },
  "message": "[gdb/testsuite] Fix port detection in gdb.debuginfod/fetch_src_and_symbols.exp\n\nOn OBS I ran into this failure with test-case\ngdb.debuginfod/fetch_src_and_symbols.exp:\n...\nFailed to listen for connections: Address already in use^M\n[Thu Oct 21 11:48:49 2021] (559/559): started http server on IPv6 port\u003d8000^M\n  ...\nFAIL: gdb.debuginfod/fetch_src_and_symbols.exp: local_url: find port timeout\n...\n\nThe test-case is trying to start debuginfod on a port to see if it\u0027s\navailable, and it handles either this message:\n  \"started http server on IPv4 IPv6 port\u003d$port\"\nmeaning success, or:\n  \"failed to bind to port\"\nmeaning failure, in which case the debuginfod instance is killed, and we try\nthe next port.\n\nThe test-case only uses the v4 address 127.0.0.1, so fix this by:\n- accepting \"started http server on IPv4 port\u003d$port\"\n- rejecting \"started http server on IPv6 port\u003d$port\"\n\nTested on x86_64-linux.\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "93490fce41efe6df23d7e400c14ea159e16020f5",
      "old_mode": 33188,
      "old_path": "gdb/testsuite/gdb.debuginfod/fetch_src_and_symbols.exp",
      "new_id": "f8fcbbae8a47a5c7dd2c1675fe6fdfd78508271f",
      "new_mode": 33188,
      "new_path": "gdb/testsuite/gdb.debuginfod/fetch_src_and_symbols.exp"
    }
  ]
}