Re: mauve test how to ?

[Stephen Crawley]

Patrice,

It looks like 'gcj' cannot compile one of the testcases.  One way
to get around this is to create a 'keys' file that excludes the
case that crashes gcj.

I've appended the mauve-kissme keys file as an example.  Note: if
you want "make KEYS=classpath" to find your file, it must live in
the Mauwe top directory and have the name "mauve-classpath".

-- Steve

----------------------------------------------------------------
# Config file that tells mauve about the `kissme' tag.
JDK1.0
JDK1.1
JDK1.2
JDK1.3
JDK1.4
JLS1.0
JLS1.1
JLS1.2
JDBC2.0

# These 2 are tests that fail to compile with JDBC2.0 but the tags don't
# seem to have the right effect.
!java.sql.Connection.TestJdbc10
!java.sql.DatabaseMetaData.TestJdbc10

# We now implement JDBC3.0 which means the following tests don't compile
!java.sql.Blob.BlobTest
!java.sql.Clob.ClobTest
!java.sql.Connection.TestJdbc20
!java.sql.DatabaseMetaData.TestJdbc20

# One of these doesn't compile, and the rest take a very long time
!java.net

# These fail to compile
!javax.naming.CompoundName
!javax.naming.CompositeName

# Character.unicode seems to be very broken (the test)
# Does not give meaningfull test results at the moment.
!java.lang.Character.unicode

# These are almost certainly buggy test cases.
# The behaviour of the garbage collector cannot be predicted.
!java.lang.ref

# This testcase is buggy ... it goes into an infinite loop with the
# current Classpath implementation of RandomAccessFile
!java.io.RandomAccessFile.raf