public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Jan Beulich <jbeulich@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r14-314] testsuite/C++: cope with IPv6 being unavailable Date: Fri, 28 Apr 2023 06:49:50 +0000 (GMT) [thread overview] Message-ID: <20230428064950.78A0D385771A@sourceware.org> (raw) https://gcc.gnu.org/g:9be54d6abad76b0d7f227687bf6b296e562d89fb commit r14-314-g9be54d6abad76b0d7f227687bf6b296e562d89fb Author: Jan Beulich <jbeulich@suse.com> Date: Fri Apr 28 08:49:35 2023 +0200 testsuite/C++: cope with IPv6 being unavailable When IPv6 is disabled in the kernel, the error message coming back from Cody::OpenInet6() is different from the sole so far expected one. gcc/testsuite/ * g++.dg/modules/bad-mapper-3.C: Relax failure pattern. Diff: --- gcc/testsuite/g++.dg/modules/bad-mapper-3.C | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/gcc/testsuite/g++.dg/modules/bad-mapper-3.C b/gcc/testsuite/g++.dg/modules/bad-mapper-3.C index ab14dd39a67..2a57956afc8 100644 --- 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" }
reply other threads:[~2023-04-28 6:49 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20230428064950.78A0D385771A@sourceware.org \ --to=jbeulich@gcc.gnu.org \ --cc=gcc-cvs@gcc.gnu.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: linkBe 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).