From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
	id 4476D385800A; Fri, 12 Jan 2024 18:23:58 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 4476D385800A
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1705083838;
	bh=YsjqOzPLm19xK1JrZ68eZgfeFhjHR4eyqiZxoN8q2vM=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=VvW5z8/onvJNwI6J/y6cngMqY5szyhiqxCrhNjjRPapDKr3n+niWHYwlRk1Ua8GWg
	 42G89HZVN6ZjAC6UNfEVIzHsUyLvCBTn6Df2NbxDDYC6uErK0Hq6yJFH/YW80J1mOp
	 LxvWQ3fy+FsrLCWBLGP2LS+oFtTcrIFNttkWto7g=
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/113355] [14 Regression] libstdc++ tests leave
 directories which can't be removed
Date: Fri, 12 Jan 2024 18:23:57 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 14.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: bug_status everconfirmed cf_reconfirmed_on
Message-ID: <bug-113355-4-DMvw97s6zu@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-113355-4@http.gcc.gnu.org/bugzilla/>
References: <bug-113355-4@http.gcc.gnu.org/bugzilla/>
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: <gcc-bugs.sourceware.org>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D113355

Jonathan Wakely <redi at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
     Ever confirmed|0                           |1
   Last reconfirmed|                            |2024-01-12

--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Those tests should clean up after themselves, so I think this happens when =
the
test run is interrupted and the tests don't finish.

I think we need a signal handler in make or dejagnu to remove them, or at l=
east
chmod them, in case the tests are interrupted with SIGINT or similar.=