public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/113355] New: [14 Regression] libstdc++ tests leave directories which can't be removed
Date: Fri, 12 Jan 2024 14:30:59 +0000 [thread overview]
Message-ID: <bug-113355-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113355
Bug ID: 113355
Summary: [14 Regression] libstdc++ tests leave directories
which can't be removed
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libstdc++
Assignee: unassigned at gcc dot gnu.org
Reporter: hjl.tools at gmail dot com
Target Milestone: ---
rm -rf build-x86_64-linux
rm: cannot remove
'build-x86_64-linux/x86_64-pc-linux-gnu/libstdc++-v3/testsuite/normal12/filesystem-test.remove_all.99037450.1WF8RD/file':
Permission denied
rm: cannot remove
'build-x86_64-linux/x86_64-pc-linux-gnu/libstdc++-v3/testsuite/normal29/filesystem-test.remove_all.2943956954.eVU7Df/file':
Permission denied
[hjl@gnu-skx-1 gcc-x32-gitlab]$ ls -l
build-x86_64-linux/x86_64-pc-linux-gnu/libstdc++-v3/testsuite/normal12/filesystem-test.remove_all.99037450.1WF8RD
total 0
-rw-r--r-- 1 hjl hjl 0 Jan 11 22:37 file
[hjl@gnu-skx-1 gcc-x32-gitlab]$ ls -l
build-x86_64-linux/x86_64-pc-linux-gnu/libstdc++-v3/testsuite/normal12/
total 4
dr-x------ 2 hjl hjl 4096 Jan 11 22:37
filesystem-test.remove_all.99037450.1WF8RD
[hjl@gnu-skx-1 gcc-x32-gitlab]$
next reply other threads:[~2024-01-12 14:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-12 14:30 hjl.tools at gmail dot com [this message]
2024-01-12 18:23 ` [Bug libstdc++/113355] " redi at gcc dot gnu.org
2024-01-12 18:24 ` redi 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-113355-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).