From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19519 invoked by alias); 19 Oct 2004 11:45:40 -0000 Mailing-List: contact mauve-discuss-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: mauve-discuss-owner@sources.redhat.com Received: (qmail 19502 invoked from network); 19 Oct 2004 11:45:39 -0000 Received: from unknown (HELO lembu.sumatrasoftware.com) (62.177.154.238) by sourceware.org with SMTP; 19 Oct 2004 11:45:39 -0000 Content-class: urn:content-classes:message Subject: RE: Object.clone() out of memory tests MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Tue, 19 Oct 2004 11:45:00 -0000 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Jeroen Frijters" To: "Stephen Crawley" Cc: "Mauve Discuss" , X-SW-Source: 2004-q4/txt/msg00015.txt.bz2 Stephen Crawley wrote: > "Jeroen Frijters" wrote: > > I'd like to move the out of memory test in > > gnu/testlet/java/lang/object/clone.java to a separate file. The test > > makes my system unbearably slow (because it pushes all memory to the > > swap file) so it would be nice to be able to disable to separately. > >=20 > > Any objections? >=20 > None from me. I made the change. > It would be nice if there was a convention of flagging tests=20 > that are in some way VM or environment specific so that they could be=20 > deselected in a Mauve key file. Yeah. On the other hand one could also argue that these tests don't belong in Mauve, but in the VM specific test suites. It turns out that the OutOfMemoryError test that I moved is also a bit dubious, because it tries to predict when the VM will throw an OutOfMemoryError, but the spec says nothing about this, it's perfectly legal for the VM to throw an OutOfMemoryError for a small allocation, but later on allow a larger allocation (e.g. due to environmental effects). Regards, Jeroen