From: Nathan Sidwell <nathan@acm.org>
To: Jan Beulich <jbeulich@suse.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Cc: Jason Merrill <jason@redhat.com>
Subject: Re: [PATCH v2] testsuite/C++: cope with IPv6 being unavailable
Date: Thu, 27 Apr 2023 18:23:27 -0400 [thread overview]
Message-ID: <07769663-f947-2889-3684-99f0f05acb8c@acm.org> (raw)
In-Reply-To: <27a0e26d-dd2d-5072-613c-8fcce513eaec@suse.com>
On 4/25/23 11:00, Jan Beulich wrote:
> When IPv6 is disabled in the kernel, the error message coming back from
> Cody::OpenInet6() is different from the sole so far expected one.
ok -- i couldn't find such a system :)
> ---
> v2: Re-base.
>
> --- a/gcc/testsuite/g++.dg/modules/bad-mapper-3.C
> +++ b/gcc/testsuite/g++.dg/modules/bad-mapper-3.C
> @@ -1,6 +1,6 @@
> // { dg-additional-options "-fmodules-ts -fmodule-mapper=localhost:172477262" }
> import unique3.bob;
> -// { dg-error {failed (connecting|disabled) mapper 'localhost:172477262'} "" { target *-*-* } 0 }
> +// { dg-error {failed (socket|connecting|disabled) mapper 'localhost:172477262'} "" { target *-*-* } 0 }
> // { dg-prune-output "fatal error:" }
> // { dg-prune-output "failed to read" }
> // { dg-prune-output "compilation terminated" }
--
Nathan Sidwell
prev parent reply other threads:[~2023-04-27 22:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-25 15:00 Jan Beulich
2023-04-27 22:23 ` Nathan Sidwell [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=07769663-f947-2889-3684-99f0f05acb8c@acm.org \
--to=nathan@acm.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=jason@redhat.com \
--cc=jbeulich@suse.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).