public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Pedro Alves <pedro@palves.net>
To: Simon Marchi <simark@simark.ca>, gdb-patches@sourceware.org
Subject: Re: [PATCH 0/2] gdb: Fix DUPLICATE and PATH regressions throughout
Date: Wed, 25 May 2022 13:47:04 +0100	[thread overview]
Message-ID: <13a54d45-19b4-018c-20bf-ad426b4a7c9b@palves.net> (raw)
In-Reply-To: <5ffd5107-ed8f-f356-52a1-8e43d2fc1c1e@simark.ca>

On 2022-05-24 16:18, Simon Marchi wrote:
> 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.

Alright, I'm going to push this.

Thanks,
Pedro Alves

      reply	other threads:[~2022-05-25 12:47 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 ` [PATCH 0/2] gdb: Fix DUPLICATE and PATH regressions throughout Simon Marchi
2022-05-25 12:47   ` Pedro Alves [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=13a54d45-19b4-018c-20bf-ad426b4a7c9b@palves.net \
    --to=pedro@palves.net \
    --cc=gdb-patches@sourceware.org \
    --cc=simark@simark.ca \
    /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).