public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Aaron Merey <amerey@redhat.com>
To: Andrew Burgess <aburgess@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb/testsuite: add a debuginfod-support.exp helper library
Date: Fri, 16 Sep 2022 17:32:17 -0400	[thread overview]
Message-ID: <CAJDtP-TbgEbgOyrQYF8fp7q+FDPWysydMvO0xutrAg8rU8BL+A@mail.gmail.com> (raw)
In-Reply-To: <20220907135136.602656-1-aburgess@redhat.com>

Hi Andrew,

On Wed, Sep 7, 2022 at 9:51 AM Andrew Burgess via Gdb-patches
<gdb-patches@sourceware.org> wrote:
>
> We currently have a single test for GDB's debuginfod support, this is
> gdb.debuginfod/fetch_src_and_symbols.exp, this script does all the
> setup, starts debuginfod, and then does the testing.
>
> This commit tries to split the existing script in two, there is a new
> library lib/debuginfod-support.exp, which contains a helper functions
> related to running debuginfod tests.  All the code in the new library
> is basically copied from the existing test case (which is why I
> retained the copyright date range on the new library), with some minor
> adjustments to try and make the code a little more generic.
>
> One change I made, for example, is the library offers functions to
> shut down debuginfod, previously we just relied on expect shutting
> down debuginfod when dejagnu completed.
>
> The existing test script is updated to make use of the new library
> code, and this test is still passing for me.  The only change in the
> test results is a single test where I changed the name to remove the
> port number from the test name - the port number can change from run
> to run, so could make it hard to compare test results.
>
> I have also done a little light house keeping on the original test
> script, updating and adding new comments, and making use of
> proc_with_prefix in a couple of places.

Thanks for cleaning this up.  The debuginfod tests all pass for me with
this patch applied on F36.  The server process correctly terminates
once the tests are finished, even if I ctrl-c part way through.

Aaron


  reply	other threads:[~2022-09-16 21:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-07 13:51 Andrew Burgess
2022-09-16 21:32 ` Aaron Merey [this message]
2022-09-20 13:59   ` Andrew Burgess

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=CAJDtP-TbgEbgOyrQYF8fp7q+FDPWysydMvO0xutrAg8rU8BL+A@mail.gmail.com \
    --to=amerey@redhat.com \
    --cc=aburgess@redhat.com \
    --cc=gdb-patches@sourceware.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).