public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@adacore.com>
To: Simon Marchi via Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] gdb/testsuite: give binaries distinct names in Ada tests
Date: Fri, 22 Jul 2022 13:16:48 -0600	[thread overview]
Message-ID: <87czdxj6u7.fsf@tromey.com> (raw)
In-Reply-To: <20220719171417.3651000-1-simon.marchi@polymtl.ca> (Simon Marchi via Gdb-patches's message of "Tue, 19 Jul 2022 13:14:16 -0400")

>>>>> "Simon" == Simon Marchi via Gdb-patches <gdb-patches@sourceware.org> writes:

Simon> Some Ada tests repeat their test sequence with different gnat-encodings,
Simon> typically "all" and "minimal".  However, they give the same name to both
Simon> binaries, meaning the second run overwrites the binary of the first run.
Simon> This makes it difficult and confusing when trying to reproduce problems
Simon> manually with the test artifacts.  Change those tests to use unique
Simon> names for each pass.

Seems like a good idea.  Thank you for doing this.

Tom

  reply	other threads:[~2022-07-22 19:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-19 17:14 Simon Marchi
2022-07-22 19:16 ` Tom Tromey [this message]
2022-07-22 19:43   ` Simon Marchi

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=87czdxj6u7.fsf@tromey.com \
    --to=tromey@adacore.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).