This is the mail archive of the
mailing list for the Mauve project.
RE: Object.clone() out of memory tests
- From: "Jeroen Frijters" <jeroen at sumatra dot nl>
- To: "Stephen Crawley" <crawley at dstc dot edu dot au>
- Cc: "Mauve Discuss" <mauve-discuss at sources dot redhat dot com>,<crawley at piglet dot dstc dot edu dot au>
- Date: Tue, 19 Oct 2004 13:45:36 +0200
- Subject: RE: Object.clone() out of memory tests
Stephen Crawley wrote:
> "Jeroen Frijters" <firstname.lastname@example.org> 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.
> > Any objections?
> None from me.
I made the change.
> It would be nice if there was a convention of flagging tests
> that are in some way VM or environment specific so that they could be
> 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).