RE: /tmp filling up when running gcc regression tests

[Dan Kegel]

Sorry I wasn't clear -- it's /tmp on the remote system that's
filling up.  The build system has 40 GB of free space, I'm
not worried about that :-)

I am working around the problem by running the following script
in the background on the remote target:

while /bin/true; do
   ls -t /tmp/*.*.* 2>/dev/null | tail +20 | xargs rm -f > /dev/null 2>&1
   sleep 60
done

- Dan

-----Original Message-----
From: Ben Elliston
To: address@hidden
Sent: 12.06.2003 20:37
Subject: Re: /tmp filling up when running gcc regression tests

Rob Savoye <address@hidden> writes:

>   Actually this is more of a problem with the GCC testsuite, not
> DejaGnu itself. I believe the test suite stashes the executables of
> test cases that have failed for post-mortem analysis. I thought it
> used to put them in the testuite directory, but it's possible things
> have been modifed to use /tmp instead.

No, it leaves them in the testsuite directory.

Ben



_______________________________________________
DejaGnu mailing list
address@hidden
http://mail.gnu.org/mailman/listinfo/dejagnu