From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27297 invoked by alias); 15 Mar 2004 16:26:51 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 27288 invoked from network); 15 Mar 2004 16:26:50 -0000 Received: from unknown (HELO localhost.redhat.com) (66.30.197.194) by sources.redhat.com with SMTP; 15 Mar 2004 16:26:50 -0000 Received: from gnu.org (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 1E7C32B92; Mon, 15 Mar 2004 11:26:50 -0500 (EST) Message-ID: <4055D949.7020506@gnu.org> Date: Mon, 15 Mar 2004 16:26:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-GB; rv:1.4.1) Gecko/20040217 MIME-Version: 1.0 To: Joel Brobecker Cc: gdb-patches@sources.redhat.com Subject: Re: [RFA/testsuite] Some feedback about bigcore.exp... References: <20040312222110.GF1135@gnat.com> In-Reply-To: <20040312222110.GF1135@gnat.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2004-03.o/txt/msg00312.txt Message-ID: <20040315162600.pMtMaqvfjUQ_qNAzpPipPm1zV4V1eP9AN0z2VzMz7qM@z> > 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 > > * gdb.base/bigcore.exp: Delete core file after test has completed. No - it will mean throwing away testsuite information. If a system is filling disk space with really large core files (as determined by du, not ls) then that system should have the test disabled -> no sparse core file support. Andrew > Sounds reasonable? > > -- Joel > > > > 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"