From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 583833858C53; Sun, 26 Feb 2023 17:26:04 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 583833858C53 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1677432364; bh=ZRWt3PSJP7A1dnQkCUTWsWA+ExoO6FGKgG1c+vTiYfY=; h=From:To:Subject:Date:In-Reply-To:References:From; b=RDiOotPUvICB0XZk37h9nN+GEJaFezG9TYkAWxUxuiUVv+MhbowO8gdr0N96COuPg d3eQv1CU5o1nCYArDl0QWBiDoQOJOKO9yRraTdpcDKy7pwjstXcu7HZL50zYpl6jRz AR4SQXRkIC/9/fhUBVWSc8uSZhQ7ZXXeH3RtplPo= From: "iains at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug d/103944] [12/13 Regression] Testsuite hang due to libphobos/testsuite/libphobos.gc/forkgc2.d Date: Sun, 26 Feb 2023 17:26:02 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: d X-Bugzilla-Version: 12.0 X-Bugzilla-Keywords: testsuite-fail X-Bugzilla-Severity: normal X-Bugzilla-Who: iains at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: ibuclaw at gdcproject dot org X-Bugzilla-Target-Milestone: 12.3 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cf_reconfirmed_on everconfirmed bug_status cc cf_gcctarget cf_known_to_fail Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D103944 Iain Sandoe changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed| |2023-02-26 Ever confirmed|0 |1 Status|UNCONFIRMED |NEW CC| |iains at gcc dot gnu.org Target|i686-redhat-linux |i686-redhat-linux, | |*-*-darwin* Known to fail| |12.2.1, 13.0 --- Comment #11 from Iain Sandoe --- On darwin, I see that the main forkgc2.exe gets killed when it times out but the child processes are still present - which leads to the testsuite hangin= g.=20 At present, skipping this test seems the best strategy for Darwin, pending a resolution.=