On 06/11/2012 06:02, Ray Kiddy wrote:
Hello -

I downloaded jtreg binaries and am running some of the tests on this machine. 
It is running 10.7.4. I am having no problems updating the source and building 
jdk7u-dev. And I can run a lot of the tests with no problems. But AWT tests 
seem not so cooperative. Is there some trick to running these?

It may be a problem that I downloaded the binaries for jtreg. Looking at the build 
dependencies was giving me a headache. And, at least with 
java/awt/appletviewer/IOExceptionIfEncodedURLTest/IOExceptionIfEncodedURLTest.sh, the 
test seems to not know what "Darwin" is? This made me suspect I need a newer 
jtreg. But this one seemed to be from the official source (i.e. 
http://download.java.net/openjdk/jtreg/).

The full results from this one are below.

I am trying to run with, for example:

        % cd jdk7u-dev
        % ../jtreg/linux/bin/jtreg \
           -jdk:build/macosx-x86_64/j2sdk-bundle/jdk1.7.0.jdk/Contents/Home \
           -w build/jtreg/test/java/awt/work -r 
build/jtreg/test/java/awt/report \
           -othervm -verbose:summary -ignore:quiet -automatic test/java/awt

I was running with -samevm. Now I am not. I added -ignore:quiet and -automatic. 
These did not do much.

If I let the tests run, they take a long time. I cannot see how long the set of 
tests should take, so I am not sure if they are hung. After a while, there are 
lots of colored windows hanging around and not much seems to be happening. Sort 
of like a lava lamp in a cubic universe.

Any info about how these test behave when things are passing would be 
appreciated.

cheers - ray

I don't know anything about the AWT tests but they don't run in samevm or agentvm mode. In jdk8 then we've added java/awt to othervm.dirs (a property in TEST.ROOT) so that they run in othervm mode even if other options are specified to jtreg. It's possible that they can't run concurrently either, but this is something that the folks on awt-dev will know.

As regards IOExceptionIfEncodedURLTest.sh then it looks to be that this hasn't been updated to work on Mac, I least I assume that is what "Unrecognized system! Darwin" is. That seems surprising as there was a big effort to update the tests to work on Mac. Maybe someone on awt-dev can say if the tests will be updated.

-Alan

Reply via email to