Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Keith Seitz via Gdb-patches <gdb-patches@sourceware.org>
To: Tom de Vries <tdevries@suse.de>, gdb-patches@sourceware.org
Subject: Re: [PATCH][gdb/testsuite] Fix port detection in gdb.debuginfod/fetch_src_and_symbols.exp
Date: Wed, 27 Oct 2021 08:35:35 -0700	[thread overview]
Message-ID: <2730eb91-ede7-ea88-e9c9-709a69961e8e@redhat.com> (raw)
In-Reply-To: <20211027102405.GA6737@delia.home>

On 10/27/21 03:24, Tom de Vries wrote:
> Hi,
> 
> On OBS I ran into this failure with test-case
> gdb.debuginfod/fetch_src_and_symbols.exp:
> ...
> Failed to listen for connections: Address already in use^M
> [Thu Oct 21 11:48:49 2021] (559/559): started http server on IPv6 port=8000^M
>    ...
> FAIL: gdb.debuginfod/fetch_src_and_symbols.exp: local_url: find port timeout
> ...
> 
> The test-case is trying to start debuginfod on a port to see if it's
> available, and it handles either this message:
>    "started http server on IPv4 IPv6 port=$port"
> meaning success, or:
>    "failed to bind to port"
> meaning failure, in which case the debuginfod instance is killed, and we try
> the next port.
> 
> The test-case only uses the v4 address 127.0.0.1, so fix this by:
> - accepting "started http server on IPv4 port=$port"
> - rejecting "started http server on IPv6 port=$port"
> 
> Tested on x86_64-linux.
> 
> Any comments?

When IPv6 is detected, the test case could set a variable to
use ::1 instead of 127.0.0.1, but that would merely test the
debuginfod client more than GDB itself, so I'd say this LGTM.

Thank you for addressing this!
Keith


  reply	other threads:[~2021-10-27 15:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-27 10:24 Tom de Vries via Gdb-patches
2021-10-27 15:35 ` Keith Seitz via Gdb-patches [this message]
2021-10-27 16:58   ` Tom de Vries via Gdb-patches

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2730eb91-ede7-ea88-e9c9-709a69961e8e@redhat.com \
    --to=gdb-patches@sourceware.org \
    --cc=keiths@redhat.com \
    --cc=tdevries@suse.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox