public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Simon Marchi <simark@simark.ca>
To: Andrew Burgess <aburgess@redhat.com>,
	Simon Marchi via Gdb-patches <gdb-patches@sourceware.org>
Cc: Simon Marchi <simon.marchi@efficios.com>
Subject: Re: [PATCH] gdb.fortran/lbound-ubound.exp: read expected lbound and ubound from function parameters (PR 30414)
Date: Thu, 18 May 2023 13:22:25 -0400	[thread overview]
Message-ID: <661cad50-9f7e-44d9-9ed8-e6503cd5bb11@simark.ca> (raw)
In-Reply-To: <87ilcq9h0y.fsf@redhat.com>

> Honestly, I wasn't even aware of perror changing the next test to
> unresolved.  So, that's my one thing learned for today :)
>
> I'm happy with using error, or no checks and just collecting the FAILs,
> whatever you prefer.
> 
> Thanks for getting this test fixed up.
> 
> Andrew

Thanks for reviewing, I will push shortly.

Simon


      reply	other threads:[~2023-05-18 17:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-04 15:48 Simon Marchi
2023-05-12 17:02 ` Andrew Burgess
2023-05-12 18:15   ` Simon Marchi
2023-05-18  8:32     ` Andrew Burgess
2023-05-18 17:22       ` Simon Marchi [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=661cad50-9f7e-44d9-9ed8-e6503cd5bb11@simark.ca \
    --to=simark@simark.ca \
    --cc=aburgess@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=simon.marchi@efficios.com \
    /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).