public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ro at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug d/95575] New: [10/11 regression] gdc.test testnames lost gdc.test prefix Date: Mon, 08 Jun 2020 09:46:44 +0000 [thread overview] Message-ID: <bug-95575-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95575 Bug ID: 95575 Summary: [10/11 regression] gdc.test testnames lost gdc.test prefix Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: d Assignee: ibuclaw at gdcproject dot org Reporter: ro at gcc dot gnu.org Target Milestone: --- As originally reported here https://gcc.gnu.org/pipermail/gcc-patches/2020-April/543045.html this patch commit c76df72f1a916d0482d15e43656ddff724352705 Author: Iain Buclaw <ibuclaw@gdcproject.org> Date: Sat Mar 28 18:44:12 2020 +0100 testsuite: Split up gdc-test.exp into each subdirectory again lost the gdc.test prefix in the testnames, as e.g. seen on Solaris: -FAIL: gdc.test/runnable/eh.d -fPIC -shared-libphobos execution test -FAIL: gdc.test/runnable/eh.d -shared-libphobos execution test -FAIL: gdc.test/runnable/test42.d execution test -FAIL: gdc.test/runnable/test42.d -g execution test -FAIL: gdc.test/runnable/test42.d -g -shared-libphobos execution test -FAIL: gdc.test/runnable/test42.d -shared-libphobos execution test +FAIL: runnable/eh.d -fPIC -shared-libphobos execution test +FAIL: runnable/eh.d -shared-libphobos execution test +FAIL: runnable/test42.d execution test +FAIL: runnable/test42.d -g execution test +FAIL: runnable/test42.d -g -shared-libphobos execution test +FAIL: runnable/test42.d -shared-libphobos execution test The testnames are supposed to be relative to gcc/testsuite.
next reply other threads:[~2020-06-08 9:46 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-06-08 9:46 ro at gcc dot gnu.org [this message] 2020-06-08 9:46 ` [Bug d/95575] " ro at gcc dot gnu.org 2020-06-08 20:36 ` ibuclaw at gdcproject dot org 2020-06-09 8:24 ` ro at CeBiTec dot Uni-Bielefeld.DE 2020-06-14 9:04 ` cvs-commit at gcc dot gnu.org 2020-06-14 9:06 ` cvs-commit at gcc dot gnu.org 2020-06-14 9:13 ` ibuclaw at gdcproject dot org
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=bug-95575-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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).