[Bug testsuite/67905] running the libstdc++ testsuite as root removed /dev/null from my system

[redi at gcc dot gnu.org]

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

--- Comment #4 from Jonathan Wakely  ---
I don't see anything in the libstdc++ testsuite that would remove it anyway, so
I'm going to blame DejaGnu or OS X.

[Bug testsuite/67905] running the libstdc++ testsuite as root removed /dev/null from my system

[egallager at gcc dot gnu.org]

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

Eric Gallager  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 CC||egallager at gcc dot gnu.org
 Resolution|--- |WORKSFORME

--- Comment #3 from Eric Gallager  ---
I'm no longer using the computer where I have to be root so this bug is no
longer relevant for me.

[Bug testsuite/67905] running the libstdc++ testsuite as root removed /dev/null from my system

[egall at gwmail dot gwu.edu]

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

--- Comment #2 from Eric Gallager  ---
Created attachment 38786
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=38786=edit
bzipped testsuite log

It happened again with yesterday's trunk. I'm attaching the logfile this time.

[Bug testsuite/67905] running the libstdc++ testsuite as root removed /dev/null from my system

[egall at gwmail dot gwu.edu]

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

--- Comment #1 from Eric Gallager  ---
Actually, disregard my previous statement about mail-report.log being
incomplete; everything ended up in it, despite the messages printed while
making it. The part about it being un-emailable was still true though; it was
only after rebooting and /dev/null successfully being recreated that I was able
to send it, which ended up as
https://gcc.gnu.org/ml/gcc-testresults/2015-10/msg00910.html