public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug d/103944] New: [12 Regression] Testsuite hang due to libphobos/testsuite/libphobos.gc/forkgc2.d
Date: Fri, 07 Jan 2022 17:07:22 +0000 [thread overview]
Message-ID: <bug-103944-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103944
Bug ID: 103944
Summary: [12 Regression] Testsuite hang due to
libphobos/testsuite/libphobos.gc/forkgc2.d
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: d
Assignee: ibuclaw at gdcproject dot org
Reporter: jakub at gcc dot gnu.org
Target Milestone: ---
When trying to build gcc 12 snapshot in fedora using rpm, make check hangs, but
what is weird is that the make process has no children and is stuck waiting on
read from a jobserver file descriptor.
Strangely, during my (almost daily) normal bootstraps/regtests I'm not seeing
this.
I think I've narrowed this down to the libphobos.gc/forkgc2.d test.
When running
make -j32 -k check-target-libphobos ALT_CC_UNDER_TEST=gcc
ALT_CXX_UNDER_TEST=g++
RUNTESTFLAGS=--target_board=unix/'{,-fstack-protector-strong}'
I see it hang, again no children, but looking in detail into
libphobos/testsuite/ I see forkgc2.exe in an unfinished log there and
./forkgc2.exe process,
killing it manually make it succeed.
next reply other threads:[~2022-01-07 17:07 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-07 17:07 jakub at gcc dot gnu.org [this message]
2022-01-07 17:09 ` [Bug d/103944] " jakub at gcc dot gnu.org
2022-01-08 3:42 ` pinskia at gcc dot gnu.org
2022-01-10 8:49 ` jakub at gcc dot gnu.org
2022-01-10 13:55 ` ibuclaw at gdcproject dot org
2022-01-10 14:10 ` jakub at gcc dot gnu.org
2022-01-10 14:30 ` jakub at gcc dot gnu.org
2022-01-10 14:52 ` ibuclaw at gdcproject dot org
2022-01-10 17:51 ` ibuclaw at gdcproject dot org
2022-05-06 8:32 ` [Bug d/103944] [12/13 " jakub at gcc dot gnu.org
2022-07-18 14:34 ` doko at gcc dot gnu.org
2023-02-26 17:26 ` iains at gcc dot gnu.org
2023-05-08 12:23 ` [Bug d/103944] [12/13/14 " rguenth at gcc dot gnu.org
2023-07-01 16:15 ` cvs-commit at gcc dot gnu.org
2023-07-03 14:24 ` cvs-commit at gcc dot gnu.org
2024-03-09 17:18 ` law at gcc dot gnu.org
2024-04-04 18:50 ` cvs-commit at gcc dot gnu.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-103944-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: 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).