From: Simon Marchi <simark@simark.ca>
To: Pedro Alves <pedro@palves.net>, gdb-patches@sourceware.org
Subject: Re: [PATCH 0/2] gdb: Fix DUPLICATE and PATH regressions throughout
Date: Tue, 24 May 2022 11:18:04 -0400 [thread overview]
Message-ID: <5ffd5107-ed8f-f356-52a1-8e43d2fc1c1e@simark.ca> (raw)
In-Reply-To: <20220519123445.2756177-1-pedro@palves.net>
On 5/19/22 08:34, Pedro Alves wrote:
> Patch #1 adds "gdb_test -nopass" as mentioned here:
>
> https://sourceware.org/pipermail/gdb-patches/2022-May/189189.html
>
> Patch #2 fixes DUPLICATE/PATH regressions throughout.
I only read the commit messages, and that all makes sense to me.
I am seeing a lot of failures on my CI due to this (it counts new DUPLICATEs
as failures), so this will help a lot bring it back to green.
Simon
next prev parent reply other threads:[~2022-05-24 15:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-19 12:34 Pedro Alves
2022-05-19 12:34 ` [PATCH 1/2] Add -nopass option to gdb_test/gdb_test_multiple Pedro Alves
2022-05-19 12:34 ` [PATCH 2/2] gdb: Fix DUPLICATE and PATH regressions throughout Pedro Alves
2022-05-20 10:10 ` [PATCH, TEST REQUEST][gdb/testsuite] Fix ERROR in gdb.ctf/funcreturn.exp Tom de Vries
2022-06-04 9:19 ` [committed][gdb/testsuite] " Tom de Vries
2022-05-24 15:18 ` Simon Marchi [this message]
2022-05-25 12:47 ` [PATCH 0/2] gdb: Fix DUPLICATE and PATH regressions throughout Pedro Alves
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=5ffd5107-ed8f-f356-52a1-8e43d2fc1c1e@simark.ca \
--to=simark@simark.ca \
--cc=gdb-patches@sourceware.org \
--cc=pedro@palves.net \
/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).