From: Tom Tromey <tromey@adacore.com>
To: Tom Tromey via Gdb-patches <gdb-patches@sourceware.org>
Cc: Tom Tromey <tromey@adacore.com>
Subject: Re: [PATCH 0/2] Suppress some FAILs
Date: Wed, 08 Feb 2023 10:18:23 -0700 [thread overview]
Message-ID: <87o7q413fk.fsf@tromey.com> (raw)
In-Reply-To: <20230123220257.3773828-1-tromey@adacore.com> (Tom Tromey via Gdb-patches's message of "Mon, 23 Jan 2023 15:02:55 -0700")
>>>>> "Tom" == Tom Tromey via Gdb-patches <gdb-patches@sourceware.org> writes:
Tom> I only see a handful of test failures on my machine. Some of the
Tom> remaining ones are being fixed (e.g., sigterm), some seem to be gdb
Tom> bugs (gdb.go), but a couple seemed needless to me.
Tom> This series fixes a couple such failures.
Tom> Let me know what you think.
I'm checking these in now.
Tom
prev parent reply other threads:[~2023-02-08 17:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-23 22:02 Tom Tromey
2023-01-23 22:02 ` [PATCH 1/2] Don't let .gdb_history file cause failures Tom Tromey
2023-01-23 22:02 ` [PATCH 2/2] Avoid FAILs in gdb.compile Tom Tromey
2023-01-24 15:41 ` Alexandra Petlanova Hajkova
2023-02-08 17:18 ` Tom Tromey [this message]
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=87o7q413fk.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).