This is the mail archive of the
mailing list for the Mauve project.
Re: Mauve patch
- From: Stephen Crawley <crawley at dstc dot edu dot au>
- To: tromey at redhat dot com
- Cc: Archie Cobbs <archie at dellroad dot org>, Sascha Brawer <brawer at dandelis dot ch>, mauve-discuss at sources dot redhat dot com, commit-classpath at gnu dot org, crawley at dstc dot edu dot au
- Date: Wed, 07 Apr 2004 16:00:37 +1000
- Subject: Re: Mauve patch
> 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 ...