RE: Mauve test question

[Jeroen Frijters]

Archie Cobbs wrote:
> Michael Koch wrote:
> >>>Why don't we start by creating an "offical" mauve-classpath
> >>>file that is CVS committed
> >>
> >>Sounds like the existing mauve-classpath file in the CVS root needs
> >>a spring-clean. Better to update that in my view than let it go
> >>stale and have a duplicate elsewhere.
> 
> Oops, didn't see that one.. yes let's only have one, so that
> would be the one to get right. Let's try to update it.

I don't think we should have a file based on black listing tests that
don't work, I'd like to have a file that simply lists all tests that are
known to be good. There are two reasons for this, the most important
being that I want to see who adds (or removes) a test to the known good
list and why (and the second that I hate scripts ;-)).

> > Is this file used at all ? And some VMs using classpath might need 
> > different contents of that file anyway. I know libgcj uses its own 
> > file called mauve-libgcj (included in libgcj).
> 
> The goal for this file should be "the right contents assuming the
> VM doesn't have any bugs". If the VM wants its own private version,
> that's that particular VM's private business. But we need a version
> that we can point to and say "if your VM is based on Classpath and
> otherwise does everything correctly then it should definitely pass
> all these tests".

Agreed. Unfortunately this means that we have to be conservative and
that some tests can never be part of it (the ones that depend on GC
behavior for example).

I've attached the list of tests that runs successfully on IKVM.

Regards,
Jeroen

zerofailure.txt
Description: zerofailure.txt