[RFA/testsuite] Some feedback about bigcore.exp...

[Joel Brobecker <brobecker@gnat.com>]

[-- Attachment #1: Type: text/plain, Size: 962 bytes --]

Hello,

Just FYI, in case others may feel the same way?

We have now run this test pretty much on most of our Unix native
platforms, and have found that the bigcore.exp testcase is usually quite
stressful for the host where the testing is being conducted. For
instance, on sparc-solaris, the system ran out of virtual memory and
swap space, and started killing processes at random. It also requires a
very large amount of disk space to be available for the core file (2GB
on x86-linux). So I was told by other fellow machine users to please
stop running this test on our build machines.

One thing I would recommend is to delete the core file once the test is
finished. I had a testsuite run that got ruined because the core file
filled up all my disk, and left no space available for the rest of the
run...

2004-03-12  J. Brobecker  <brobecker@gnat.com>

        * gdb.base/bigcore.exp: Delete core file after test has completed.

Sounds reasonable?

-- 
Joel

[-- Attachment #2: bigcore.exp --]
[-- Type: text/plain, Size: 506 bytes --]

Index: bigcore.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.base/bigcore.exp,v
retrieving revision 1.4
diff -u -r1.4 bigcore.exp
--- bigcore.exp	27 Feb 2004 16:48:03 -0000	1.4
+++ bigcore.exp	12 Mar 2004 22:17:59 -0000
@@ -190,3 +190,7 @@
 
 check_heap next $next_heap
 check_heap prev $prev_heap
+
+# The generated core file uses a large amount of disk-space, so we
+# delete it now that we're done.
+remote_exec build "rm -f $corefile"