public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug libstdc++/113355] New: [14 Regression] libstdc++ tests leave directories which can't be removed
@ 2024-01-12 14:30 hjl.tools at gmail dot com
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
0 siblings, 2 replies; 3+ messages in thread
From: hjl.tools at gmail dot com @ 2024-01-12 14:30 UTC (permalink / raw)
To: gcc-bugs
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]$
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug libstdc++/113355] [14 Regression] libstdc++ tests leave directories which can't be removed
2024-01-12 14:30 [Bug libstdc++/113355] New: [14 Regression] libstdc++ tests leave directories which can't be removed hjl.tools at gmail dot com
@ 2024-01-12 18:23 ` redi at gcc dot gnu.org
2024-01-12 18:24 ` redi at gcc dot gnu.org
1 sibling, 0 replies; 3+ messages in thread
From: redi at gcc dot gnu.org @ 2024-01-12 18:23 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113355
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 least
chmod them, in case the tests are interrupted with SIGINT or similar.
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug libstdc++/113355] [14 Regression] libstdc++ tests leave directories which can't be removed
2024-01-12 14:30 [Bug libstdc++/113355] New: [14 Regression] libstdc++ tests leave directories which can't be removed hjl.tools at gmail dot com
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
1 sibling, 0 replies; 3+ messages in thread
From: redi at gcc dot gnu.org @ 2024-01-12 18:24 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113355
--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
This isn't a regression though, it's always been that way.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2024-01-12 18:24 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2024-01-12 14:30 [Bug libstdc++/113355] New: [14 Regression] libstdc++ tests leave directories which can't be removed hjl.tools at gmail dot com
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
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).