From: Andrew Burgess <aburgess@redhat.com>
To: gdb-patches@sourceware.org
Cc: Andrew Burgess <aburgess@redhat.com>
Subject: [PATCH 0/2] A few minor testsuite cleanups
Date: Wed, 29 Nov 2023 17:55:42 +0000 [thread overview]
Message-ID: <cover.1701280438.git.aburgess@redhat.com> (raw)
Patch #1 fixes a timeout in gdb.ada/complete.exp when READ1 is used.
Patch #2 performs some wider cleanup, inspired by patch #1.
Andrew Burgess (2):
gdb/testsuite: fix gdb.ada/complete.exp timeout in READ1 mode
gdb/testsuite: tighten up some end-of-line patterns
gdb/testsuite/gdb.ada/catch_assert_if.exp | 2 +-
gdb/testsuite/gdb.ada/catch_ex.exp | 2 +-
gdb/testsuite/gdb.ada/complete.exp | 19 ++++++++++++++-----
gdb/testsuite/gdb.ada/dyn_loc.exp | 2 +-
gdb/testsuite/gdb.ada/excep_handle.exp | 2 +-
gdb/testsuite/gdb.ada/frame_args.exp | 2 +-
gdb/testsuite/gdb.ada/info_types.exp | 4 ++--
gdb/testsuite/gdb.base/info-target.exp | 2 +-
gdb/testsuite/gdb.base/nofield.exp | 2 +-
gdb/testsuite/gdb.cp/local.exp | 2 +-
gdb/testsuite/gdb.stabs/exclfwd.exp | 20 +++++++++++---------
11 files changed, 35 insertions(+), 24 deletions(-)
base-commit: 87853585d89dac22c97020ad8af0c3abe2ce6d17
--
2.25.4
next reply other threads:[~2023-11-29 17:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-29 17:55 Andrew Burgess [this message]
2023-11-29 17:55 ` [PATCH 1/2] gdb/testsuite: fix gdb.ada/complete.exp timeout in READ1 mode Andrew Burgess
2023-11-30 19:22 ` Tom Tromey
2023-11-29 17:55 ` [PATCH 2/2] gdb/testsuite: tighten up some end-of-line patterns Andrew Burgess
2023-11-30 19:23 ` Tom Tromey
2023-12-08 22:25 ` Tom de Vries
2023-12-09 6:59 ` Tom de Vries
2023-12-11 14:52 ` Andrew Burgess
2023-12-11 14:55 ` Tom de Vries
2023-12-11 16:16 ` Tom de Vries
2023-12-11 16:44 ` Andrew Burgess
2023-12-08 18:07 ` [PATCH 0/2] A few minor testsuite cleanups 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.1701280438.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).