Re: Jikes RVM & mauve tests

[Mark Wielaard]

Hi,

On Fri, 2003-01-31 at 23:57, David P Grove wrote:
>       I've been experimenting a little bit with running Mauve tests on top
> of Jikes RVM and GNU Classpath.  This generally does pretty well, except
> that there are massive failures on java.lang.Character.unicode ("make check
> KEYS=!java. java.lang.Character" yields 136460 of 3603803 tests failed).
> Before looking into this further, I just wanted to verify that the
> classpath libraries are expected to pass these tests.

Both Kissme and gcj disable this test by default. If I remember
correctly they are based on an old unicode spec.

>       On the bright side, "make check KEYS=!java.net
> !java.lang.Character.unicode" yields 127 of 2017 tests failed.  Roughly
> half of these failures are because Jikes RVM has never bothered to
> implement thread priorities (easily fixed).

Note that there are still deficiencies in Classpath that can explain
some of these failures. With kissme and the above KEYS I get:
74 of 2037 tests failed

Brian has results posted on:
http://www.haphazard.org/~cbj/classpath/automauve/summary.html
And I reqularly post results on gcc-testresults for gcj. See for the
latests: http://gcc.gnu.org/ml/gcc-testresults/2003-01/msg01418.html
(Note that gcj uses a exclude file and an xfail file.)

>       I excluded java.net because of the following javac compilation
> problem...is this expected?
> public class TestSocketImplFactory
>        ^
> gnu/testlet/java/net/Socket/SocketTest.java:203: Socket() has protected
> access in java.net.Socket
>       sock = new Socket (); // unconnected socket
> 

The no argument constructor is public in Classpath (specnote says since
1.4). I never noticed this since I use either gcj or jikes with the
Classpath libraries to compile Mauve.

Maybe we could move that part of the test into a new Socket14.java
testlet that explicitly sets Tags: JDK1.4.

Cheers,

Mark