From: Stephen Crawley <crawley@dstc.edu.au>
To: tromey@redhat.com
Cc: Archie Cobbs <archie@dellroad.org>,
Sascha Brawer <brawer@dandelis.ch>,
mauve-discuss@sources.redhat.com, commit-classpath@gnu.org,
crawley@dstc.edu.au
Subject: Re: Mauve patch
Date: Wed, 07 Apr 2004 06:01:00 -0000 [thread overview]
Message-ID: <200404070600.i3760YmT005287@piglet.dstc.edu.au> (raw)
In-Reply-To: Message from Tom Tromey <tromey@redhat.com> of "06 Apr 2004 23:31:38 CST." <87vfkc4amd.fsf@fleche.redhat.com>
Hi Tom,
> Perhaps it is better to just remove the test.
That would be my preferred option.
> Or make a new "unportable" section of Mauve, since some things
> seemingly can't be tested.
I think it would be better for each JVM projects to manage its own
non-portable testcases. In Kissme for example, there is a small
regression testsuite (called "HitMe") that tests some of Kissme's low
level and VM specific features.
The HitMe harness assumes that less of the VM infrastructure is working
that the Mauve harness does. There is even a version that avoids using
java.lang.io.* and uses the rc returned using System.exit() to signal
test success / failure. Some HitMe tests require special Kissme
commandline arguments. The makefile understands this ...
-- Steve
next prev parent reply other threads:[~2004-04-07 6:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200404060330.i363UY1B018067@arch20m.dellroad.org>
2004-04-06 11:52 ` Sascha Brawer
2004-04-06 12:15 ` Ingo Prötel
2004-04-06 14:08 ` Archie Cobbs
2004-04-07 5:45 ` Tom Tromey
2004-04-07 6:01 ` Stephen Crawley [this message]
2004-04-07 14:53 ` Archie Cobbs
2004-04-15 21:04 ` Mark Wielaard
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=200404070600.i3760YmT005287@piglet.dstc.edu.au \
--to=crawley@dstc.edu.au \
--cc=archie@dellroad.org \
--cc=brawer@dandelis.ch \
--cc=commit-classpath@gnu.org \
--cc=mauve-discuss@sources.redhat.com \
--cc=tromey@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).