Re: mauve test configure file?

[Mark Wielaard <mark at klomp dot org>]

Hi,

On Sat, 2003-02-22 at 15:07, Andreas Tobler wrote:
> for the first run it doesn't look that bad?
> I only ran the mauve part.

This does look good. I have added comments for the tests were I know
what is wrong. (I have CCed java at gcc dot gnu dot org so others know of the
status).

> FAIL: gnu.testlet.java.io.File.jdk11: getCanonicalPath () (number 1)
> FAIL: gnu.testlet.java.io.OutputStreamWriter.jdk11: IOException 
> unexpected (number 1)

Don't know what goes wrong here.

> FAIL: gnu.testlet.java.lang.Double.DoubleTest: Error: 
> test_shortbyteValue failed - 5 (number 1)
> FAIL: gnu.testlet.java.lang.Float.FloatTest: Error: test_shortbyteValue 
> failed - 5 (number 1)

I have these two. They seem to be powerpc related.
But I also have the following which you don't seem to have:
FAIL: gnu.testlet.java.lang.Double.DoubleTest: Error: test_longValue returned wrong results CYGNUS: Float to int conversions - 1 (number 1)

> FAIL: gnu.testlet.java.lang.Math.MathTest: Error : test_pow failed - 9 
> (number 1)
> FAIL: gnu.testlet.java.lang.Math.sin (number 1)

These seem to work for me.

> WARNING: program timed out.

Time out? Can you see which test this is?

> FAIL: gnu.testlet.java.lang.String.getBytes13: String.getBytes("Cp1252") 
> (number 1)
> FAIL: gnu.testlet.java.lang.String.getBytes14: 
> String.getBytes("windows-1252") (number 1)

These two are the same encodings under different names (aliases).
Do you have iconv? Are they listed in iconv --list?

> FAIL: gnu.testlet.java.lang.String.getBytes14: 
> String.getBytes("ISO-8859-15") (number 1)

This is a common alias for ISO8859-15 which we should probably just add
to out own encoding alias tables.

> WARNING: program timed out.

Another timeout?

> FAIL: gnu.testlet.java.net.DatagramSocket.DatagramSocketTest: Error : 
> test_Basics failed - 8  (number 1)
> FAIL: gnu.testlet.java.net.DatagramSocket.DatagramSocketTest2: 
> invalid_receive_data: test 1 - Should NOT throw Exception (number 1)
> FAIL: gnu.testlet.java.net.DatagramSocket.DatagramSocketTest2: 
> invalid_send_addr: test 1 - Should NOT throw Exception (number 1)
> FAIL: gnu.testlet.java.net.DatagramSocket.DatagramSocketTest2: 
> invalid_send_port: test 1 - Should NOT throw Exception (number 1)
> FAIL: gnu.testlet.java.net.DatagramSocket.DatagramSocketTest2: 
> invalid_send_data: test 1 - Should NOT throw Exception (number 1)
> FAIL: gnu.testlet.java.net.MulticastSocket.MulticastSocketTest: Correct 
> args. - 3 (number 1)
> FAIL: gnu.testlet.java.net.MulticastSocket.MulticastSocketTest: Correct 
> args. different constructor. - 4 (number 1)
> FAIL: gnu.testlet.java.net.MulticastSocket.MulticastSocketTest: 
> joinGroup() with incorrect params. should have thrown a 
> NullPointerException - 5a (number 1)
> FAIL: gnu.testlet.java.net.MulticastSocket.MulticastSocketTest: 
> leaveGroup() with incorrect params. should have thrown a 
> NullPointerException - 7a (number 1)
> FAIL: gnu.testlet.java.net.MulticastSocket.MulticastSocketTest: Correct 
> args. - 8 (number 1)
> FAIL: gnu.testlet.java.net.MulticastSocket.MulticastSocketTest: Should 
> not have thrown any exception - 11 (number 1)
> FAIL: gnu.testlet.java.net.Socket.SocketTest: Error : test_Basics failed 
> - 2 Unknown host exception should have been thrown here. (number 1)
> FAIL: gnu.testlet.java.net.Socket.SocketTest: Error : test_params failed 
> - 1 get port did not return proper values (number 1)
> FAIL: gnu.testlet.java.net.Socket.jdk13: unexpected error: Interrupted 
> system call (number 1)

I am seeing some of these to. Haven't analysed them yet. Note that for
some of these you need a internet connection that can reach the
sources.redhat.com machine.

> FAIL: gnu.testlet.java.util.Properties.AcuniaPropertiesTest: v does not 
> contain:\$-- listing properties --\$ (number 1)
> FAIL: gnu.testlet.java.util.Properties.AcuniaPropertiesTest: v does not 
> contain:\$-- listing properties --\$ (number 1)
> FAIL: gnu.testlet.java.util.Properties.AcuniaPropertiesTest: should 
> throw an NullPointerEception instead of: java.lang.NullPointerException 
> (number 1)
> FAIL: gnu.testlet.java.util.Properties.AcuniaPropertiesTest: should 
> throw an NullPointerEception instead of: java.lang.NullPointerException 
> (number 1)

Some of these showed up after the recent Properties patch. But I don't
trust this test. Have to go through it and see if it is correct.

> FAIL: gnu.testlet.java.util.zip.ZipEntry.newZipEntry: name larger then 
> 65535 chars (number 1)
> FAIL: gnu.testlet.java.util.zip.ZipEntry.setComment: uncaught exception 
> at "comment larger then 65535 chars" number 2: 
> java.lang.NullPointerException

These are new tests. Just added fixes for these two tests to libgcj
yesterday. Update from CVS and they should disappear.

You don't seem to have the following failures which I am seeing:
FAIL: gnu.testlet.java.security.SecureRandom.Instance: uncaught exception at  number 1: java.lang.InternalError: no SHA implementation found
FAIL: gnu.testlet.java.security.SecureRandom.SHA1PRNG: found implementation (number 1)
FAIL: gnu.testlet.java.security.SecureRandom.SHA1PRNG: no implementation found (number 1)
FAIL: gnu.testlet.java.security.Security.property: uncaught exception at  number 1: java.lang.NullPointerException

Maybe those occur because I don't do a make install before running make
check. Have to test that.

Cheers,

Mark