From: Andrew Burgess <aburgess@redhat.com>
To: gdb-patches@sourceware.org
Cc: Andrew Burgess <aburgess@redhat.com>
Subject: [PATCH 0/2] Fix remaining gdb.trace/ duplicate test names
Date: Thu, 1 Feb 2024 13:04:04 +0000 [thread overview]
Message-ID: <cover.1706792515.git.aburgess@redhat.com> (raw)
I went ahead and pushed a couple of patches to fix some duplicate test
names. They were all the "obvious" changes. This series contains the
last few fixes for gdb.trace/*, but these are heading towards non-obvious.
If there's no feedback I'll go ahead and push these some time next week.
---
Andrew Burgess (2):
gdb/testsuite: fix some more duplicate test names in gdb.trace/
gdb/testsuite: fix duplicate test names in gdb.trace/circ.exp
gdb/testsuite/gdb.trace/circ.exp | 76 +++++++++++++++----------
gdb/testsuite/gdb.trace/ftrace-lock.exp | 45 +++++++--------
gdb/testsuite/gdb.trace/trace-mt.exp | 56 ++++++++----------
3 files changed, 91 insertions(+), 86 deletions(-)
base-commit: 05d1b4b4ad7d74a64cc71c53d621241fc393fcb6
--
2.25.4
next reply other threads:[~2024-02-01 13:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-01 13:04 Andrew Burgess [this message]
2024-02-01 13:04 ` [PATCH 1/2] gdb/testsuite: fix some more duplicate test names in gdb.trace/ Andrew Burgess
2024-02-01 13:04 ` [PATCH 2/2] gdb/testsuite: fix duplicate test names in gdb.trace/circ.exp Andrew Burgess
2024-03-05 16:36 ` [PATCH 0/2] Fix remaining gdb.trace/ duplicate test names 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=cover.1706792515.git.aburgess@redhat.com \
--to=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).