jtreg testing integrated

[Mark Wielaard]

Hi Andrew (Tom/Lillian CCed because of the mauve test section below),

On Mon, 2008-05-19 at 15:56 +0100, Andrew John Hughes wrote:
> Thanks for doing this.  I'm certainly interested in a version of jtreg
> that doesn't depend on half the Java universe.

Well, it wasn't that bad :) And I am sure I removed some functionality
(like the ant and junit integration) that is really useful for somebody
else.

> Well my guess would be that the changes from proprietary JDK to
> OpenJDK invalidate
> a lot of these tests.  The crypto failures I guess will be looking for
> an algorithm that's not
> in the crypto that was finally released.

Yes, some of the crypto related fails seem to depend on some old
(obfuscated) names of the old provider.

> In summary, in most cases it's the tests that need fixing.

I do believe most fails can be resolved by actually cleaning up the
tests indeed.

> > If possible it would be nice if distributions could integrate this into
> > their package build process and make the results available just like the
> > integrated mauve testing the fedora and ubuntu are now doing (would
> > someone care to integrate that into the icedtea build proper?)
>
> I'd be interested to see the results -- do all Mauve tests now pass for IcedTea?

The fedora build log of icedtea can be found at:
http://koji.fedoraproject.org/koji/packageinfo?packageID=5920
The mauve results are part of the actual build.log like:
http://koji.fedoraproject.org/koji/getfile?taskID=596057&name=build.log
(Warning! Very big! Mauve results should be at the end, look for "MAUVE
TESTING", except that they aren't because of errors... Lillian/Tom could
you take a look at that?)

Cheers,

Mark