Running OpenJDK regression tests with 'jtreg -gui' fails

Wed Oct 2 02:46:38 PDT 2013

Hi Jonathan,

thanks for your fast response. I've retried my tests and it seems I
was a little confused by the versions in my last mail. Version 4.1b05
works for me as well:

jtreg, version 4.1 fcs b05
Installed in /share/software/Java/jtreg-4.1-bin-b05/lib/jtreg.jar
Running on platform version 1.7.0_09 from /share/software/Java/jdk1.7.0_09/jre.
Built with Java(TM) 2 SDK, Version 1.5.0-b64 on November 29, 2012.
Copyright (c) 1999, 2012, Oracle and/or its affiliates. All rights reserved.
Use is subject to license terms.
TestNG: version 6.7-201209281340

It was version 4.1b02 that didn't work and gave the stacktrace I send
you in my last mail:

jtreg, version 4.1 fcs b02
Installed in /share/software/Java/jtreg-4.1-bin-b02/lib/jtreg.jar
Running on platform version 1.7.0_09 from /share/software/Java/jdk1.7.0_09/jre.
Built with Java(TM) 2 SDK, Version 1.5.0-b64 on May 21, 2010.
Copyright 2008 Sun Microsystems, Inc. All Rights Reserved.
Use is subject to license terms.

I also saw the message about "-J followed by a space" yesterday but
unfortunaltely I can not reproduce that today any more.

And I'm also a little confused by the different versions. The latest
version I could find is the one Richard Warburton provided at
http://insightfullogic.com/media/jtreg.zip as reaction to the mail
thread http://mail.openjdk.java.net/pipermail/jtreg-use/2013-September/000258.html.
It works as well, but it reports the following version:

jtreg, version 4.0 dev b00
Installed in /share/software/Java/jtreg_Richard_Warburton/lib/jtreg.jar
Running on platform version 1.7.0_09 from /share/software/Java/jdk1.7.0_09/jre.
Built with 1.7.0_25 on 09/25/2013 12:45 AM.
Copyright (c) 1999, 2013, Oracle and/or its affiliates. All rights reserved.
Use is subject to license terms.
TestNG: version unknown

which seems to be even older than the one from 4.1b02.

This lets me think that the problem may be not caused by jtreg but by
jtharness instead. And indeed jtreg 4.1b02 comes with an old version
of jtharness:

JT Harness, version 4.1.4 MR1 b17
Installed in /share/software/Java/jtreg-4.1-bin-b02/lib/javatest.jar
Running on platform version 1.7.0_09 from /share/software/Java/jdk1.7.0_09/jre.
Built with Java(TM) 2 SDK, Version 1.5.0 on August 29, 2008.
Copyright (C) 1996-2008 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.

While 4.1b05 and Richard Warburton's binaries have newer versions of jtharness:

JT Harness, version 4.4 MR1 b19
Installed in /share/software/Java/jtreg-4.1-bin-b05/lib/javatest.jar
Running on platform version 1.7.0_09 from /share/software/Java/jdk1.7.0_09/jre.
Built with Java(TM) 2 SDK, Version 1.6.0 on June 23, 2011.
Copyright (c) 2001, 2011, Oracle and/or its affiliates. All rights reserved.

JT Harness, version 4.4.1 MR1 b13
Installed in /share/software/Java/jtreg_Richard_Warburton/lib/javatest.jar
Running on platform version 1.7.0_09 from /share/software/Java/jdk1.7.0_09/jre.
Built with Java(TM) 2 SDK, Version 1.6.0 on December 20, 2011.
Copyright (c) 2001, 2011, Oracle and/or its affiliates. All rights reserved.

So this is really all quite confusing! I would suggest to update the
OpenJDK jtreg build page at http://openjdk.java.net/jtreg/build.html
and request at least version 4.4 as build requirement for jtreg. I
think it would also be helpful if the top-level OpenJDK jtreg page at
http://openjdk.java.net/jtreg/ would provide a download link for jtreg
4.1b05 because that's apparently the last version that works and which
is available for download from http://download.java.net/openjdk/jtreg

Thanks for your support and best regards,
Volker

On Wed, Oct 2, 2013 at 4:06 AM, Jonathan Gibbons
<jonathan.gibbons at oracle.com> wrote:
> On 10/01/2013 09:13 AM, Volker Simonis wrote:
>>
>> Hi,
>>
>> maybe this is a silly question, but I'm not able to run the jtreg
>> tests from jdk/tests directory in GUI mode (i.e. by running jtreg with
>> the '-gui' option).
>>
>> If I run the test from the command line, everything works perfect. E.g.
>>
>> JT_JAVA=/jdk1.7.0_09 /jtreg/linux/bin/jtreg -jdk:/jdk1.7.0_09
>> -w:/tmp/JTwork -r:/tmp/JTreport -v java/lang/Boolean
>>
>> successfully runs the 4 tests under java/lang/Boolean.
>>
>> If I however use:
>>
>> JT_JAVA=/jdk1.7.0_09 /jtreg/linux/bin/jtreg -jdk:/jdk1.7.0_09
>> -w:/tmp/JTwork -r:/tmp/JTreport -v -gui java/lang/Boolean
>>
>> the jtreg-GUI appears and lists all the JDK tests in the left window.
>> Now no difference which tests I select and execute, they always fail
>> with the error " Error. Unexpected exception caught from test
>> java/lang/Byte/Decode.java: java.lang.NullPointerException". The stack
>> trace looks as follows:
>>
>> java.lang.NullPointerException
>>      at
>> com.sun.javatest.regtest.RegressionScript.run(RegressionScript.java:135)
>>      at com.sun.javatest.Script.run(Script.java:228)
>>      at
>> com.sun.javatest.DefaultTestRunner.runTest(DefaultTestRunner.java:167)
>>      at
>> com.sun.javatest.DefaultTestRunner.access$100(DefaultTestRunner.java:43)
>>      at
>> com.sun.javatest.DefaultTestRunner$1.run(DefaultTestRunner.java:66)
>>
>> It seems that for some reason, the Java-files are not compiled to
>> classfiles and executed as shell scripts, but I have no idea why this
>> happens. As stated before, without the '-gui' option, everything works
>> perfectly.
>>
>> Any idea what I'm doing wrong?
>>
>> Thank you and best regards,
>> Volker
>>
>> PS: I've tested this with different java version (from 6 to 8) and
>> different jtreg versions (4.1-bin-b02 and 4.1-bin-b05) on Ubuntu 12.04
>> Linux all with the same result.
>
>
> Volker,
>
> I played with this a bit but could not exactly recreate your failure.
> The java/lang/Boolean tests always passed for me, but I did see
> compilation errors for the subsequent tests (e.g. java/lang/Byte)
> when using jtreg b05.   (I got a message about -J followed by a
> space.  But when I switched to using the latest version of jtreg,
> all those problems went away.
>
> So, as much as I don't like it when someone asks, "have you tried
> the latest version?", I have to ask, "have you tried the latest version
> of jtreg?".
>
> Also, for the stack trace you reported, what version of jtreg were
> you using at the time?
>
> -- Jon
>