mauve test configure file?

Sat Feb 22 17:37:00 GMT 2003

Hi Mark,
Mark Wielaard wrote:
> This does look good. I have added comments for the tests were I know
> what is wrong. (I have CCed java@gcc.gnu.org so others know of the
> status).

And I didn't cc java@gcc.gnu.org since it was a first run and I had a 
massive swapping happen during the tests. I ran in parallel a bootstrap 
and so not all results seem to me reliable. So I guess some timeout are 
coming from there.
I stripped the comments since I re run the tests on a 3.3 build from 
today soon. If the failures come up again I analyze further.
>>WARNING: program timed out.

Probably swapping issue. The Book was frozen somehow.
>>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?

No, I don't have iconv installed, may I should try?
>>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.

Yes, I remember this writing style from Xfree86. There I saw these 
'aliases'.
> 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.

Well, I am in a 192.168 segment with cable access?
> 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.

I didn't do an install either. Just out of the build tree a make check 
RUNTESTFLAGS...
Thank you for feedback.
Andreas