From: "Jeroen Frijters" <jeroen@sumatra.nl>
To: "Stephen Crawley" <crawley@dstc.edu.au>
Cc: "Mauve Discuss" <mauve-discuss@sources.redhat.com>,
<crawley@piglet.dstc.edu.au>
Subject: RE: Object.clone() out of memory tests
Date: Tue, 19 Oct 2004 11:45:00 -0000 [thread overview]
Message-ID: <D92197D0A6547B44A1567814F851FA687EB9@LEMBU.sumatrasoftware.com> (raw)
Stephen Crawley wrote:
> "Jeroen Frijters" <jeroen@sumatra.nl> 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).
Regards,
Jeroen
next reply other threads:[~2004-10-19 11:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-19 11:45 Jeroen Frijters [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-10-17 14:04 Jeroen Frijters
2004-10-17 23:26 ` Stephen Crawley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=D92197D0A6547B44A1567814F851FA687EB9@LEMBU.sumatrasoftware.com \
--to=jeroen@sumatra.nl \
--cc=crawley@dstc.edu.au \
--cc=crawley@piglet.dstc.edu.au \
--cc=mauve-discuss@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).