From: <jal...@wo...> - 2004-05-28 10:56:41
|
Jikes RVM Mauve test summary for Fri May 28 03:05:45 EDT 2004 0 tests passed 0 tests failed Jikes RVM Regression tests against classpath CVS head for Fri May 28 03:05:45 EDT 2004 Ran 30 Passed 0 Failed 30 Failure Details --------------- prototype: Failed in gctest prototype: Failed in bytecodeTests prototype: Failed in opttests prototype: Failed in reflect prototype: Failed in threads prototype: Failed in jni prototype: Failed in CaffeineMark prototype: Failed in jBYTEmark prototype: Failed in javalex prototype: Failed in xerces prototype: Failed in xalan prototype: Failed in soot prototype: Failed in ipsixql prototype: Failed in SPECjvm98 prototype: Failed in SPECjbb2000 development: Failed in gctest development: Failed in bytecodeTests development: Failed in opttests development: Failed in reflect development: Failed in threads development: Failed in jni development: Failed in CaffeineMark development: Failed in jBYTEmark development: Failed in javalex development: Failed in xerces development: Failed in xalan development: Failed in soot development: Failed in ipsixql development: Failed in SPECjvm98 development: Failed in SPECjbb2000 The config used for the mauve tests was JDK1.0 JDK1.1 JDK1.2 JDK1.3 JDK1.4 JLS1.0 JLS1.1 JLS1.2 JDBC1.0 JDBC2.0 # This test sets the socket factory to a bogus implementation # that causes all subsequent tests to fail !java.net.Socket.setSocketImplFactory # avoid bashing our sockets # Tests are not useful...can't be this precise in how JVM deals with references !java.lang.ref. # Silly tests that cause problems in automated testing script !java.io.File.security # exclusions due to defects in Jikes RVM !java.net.DatagramSocket # hangs Jikes RVM !java.net.DatagramPacket # hangs Jikes RVM !java.net.MulticastSocket # hangs Jikes RVM !java.net.ServerSocket # hangs Jikes RVM !java.net.URLClassLoader.getResourceRemote # hangs Jikes RVM !java.awt.image.PixelGrabber # problem with gtkpeer function vector? |