From volker.simonis at gmail.com Tue Oct 1 09:13:01 2013 From: volker.simonis at gmail.com (Volker Simonis) Date: Tue, 1 Oct 2013 18:13:01 +0200 Subject: Running OpenJDK regression tests with 'jtreg -gui' fails Message-ID: 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. From jonathan.gibbons at oracle.com Tue Oct 1 11:48:25 2013 From: jonathan.gibbons at oracle.com (Jonathan Gibbons) Date: Tue, 01 Oct 2013 11:48:25 -0700 Subject: Running OpenJDK regression tests with 'jtreg -gui' fails In-Reply-To: References: Message-ID: <524B18F9.9080608@oracle.com> I'll file a high priority bug to investigate this. -- Jon 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. From jonathan.gibbons at oracle.com Tue Oct 1 12:49:52 2013 From: jonathan.gibbons at oracle.com (Jonathan Gibbons) Date: Tue, 01 Oct 2013 12:49:52 -0700 Subject: Running OpenJDK regression tests with 'jtreg -gui' fails In-Reply-To: <524B18F9.9080608@oracle.com> References: <524B18F9.9080608@oracle.com> Message-ID: <524B2760.1000009@oracle.com> This is being tracked as https://bugs.openjdk.java.net/browse/CODETOOLS-7900233 -- Jon On 10/01/2013 11:48 AM, Jonathan Gibbons wrote: > I'll file a high priority bug to investigate this. > > -- Jon > > 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. > From jonathan.gibbons at oracle.com Tue Oct 1 19:06:37 2013 From: jonathan.gibbons at oracle.com (Jonathan Gibbons) Date: Tue, 01 Oct 2013 19:06:37 -0700 Subject: Running OpenJDK regression tests with 'jtreg -gui' fails In-Reply-To: References: Message-ID: <524B7FAD.3050400@oracle.com> 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 From volker.simonis at gmail.com Wed Oct 2 02:46:38 2013 From: volker.simonis at gmail.com (Volker Simonis) Date: Wed, 2 Oct 2013 11:46:38 +0200 Subject: Running OpenJDK regression tests with 'jtreg -gui' fails In-Reply-To: <524B7FAD.3050400@oracle.com> References: <524B7FAD.3050400@oracle.com> Message-ID: 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 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 > From martinrb at google.com Wed Oct 2 15:53:49 2013 From: martinrb at google.com (Martin Buchholz) Date: Wed, 2 Oct 2013 15:53:49 -0700 Subject: Can't Compile jtreg In-Reply-To: <51F7FEC1.4020608@oracle.com> References: <51DF2F1B-5307-49F9-AA0D-C6EAE78B802F@nicholaswilliams.net> <51F7F0C6.60709@oracle.com> <51F7F3C6.4090208@oracle.com> <1422892F-4095-4D10-A2C3-150F7A2DCC03@nicholaswilliams.net> <51F7F7F7.60504@oracle.com> <05BB8850-52EC-40AD-8F5D-B5B411EFE1C8@nicholaswilliams.net> <51F7FA90.4000801@oracle.com> <8345387A-86AF-4ACE-AD1B-724A2007B369@nicholaswilliams.net> <51F7FEC1.4020608@oracle.com> Message-ID: Hi Jonathan, Your fixes to only use JCOV in an Oracle environment didn't quite work for me. Here's a small patch to fix an obvious little bug, after which I can build jtreg successfully (it's still not actually easy, with all the dependencies). diff --git a/make/jtreg.gmk b/make/jtreg.gmk --- a/make/jtreg.gmk +++ b/make/jtreg.gmk @@ -350,7 +350,7 @@ # # import JCov -#ifdef JCOV_HOME +ifdef JCOV_HOME $(JTREG_IMAGEDIR)/lib/jcov.jar: $(JCOV_HOME)/lib/jcov.jar $(RM) -f $@ @@ -366,7 +366,7 @@ $(JTREG_IMAGEDIR)/lib/jcov.jar \ $(JTREG_IMAGEDIR)/lib/jcov_implant.jar -#endif JCOV_HOME +endif JCOV_HOME #---------------------------------------------------------------------- # On Tue, Jul 30, 2013 at 10:58 AM, Jonathan Gibbons < jonathan.gibbons at oracle.com> wrote: > On 07/30/2013 10:51 AM, Nick Williams wrote: > >> On Jul 30, 2013, at 12:40 PM, Jonathan Gibbons wrote: >> >> On 07/30/2013 10:33 AM, Nick Williams wrote: >>> >>>> On Jul 30, 2013, at 12:29 PM, Jonathan Gibbons wrote: >>>> >>>> On 07/30/2013 10:25 AM, Nick Williams wrote: >>>>> >>>>>> On Jul 30, 2013, at 12:11 PM, Jonathan Gibbons wrote: >>>>>> >>>>>> On 07/30/2013 10:04 AM, Nick Williams wrote: >>>>>>> >>>>>>>> On Jul 30, 2013, at 11:58 AM, Jonathan Gibbons wrote: >>>>>>>> >>>>>>>> On 07/30/2013 09:19 AM, Nick Williams wrote: >>>>>>>>> >>>>>>>>>> First, please let me say that the build readme at >>>>>>>>>> http://openjdk.java.net/jtreg/**build.html(and in HG) is sorely lacking. Here's what I've learned on my own so far, >>>>>>>>>> from analyzing error messages and reading Defs.gmk: >>>>>>>>>> >>>>>>>>>> - JAVAHELP_HOME, which usually points to the JavaHelp home >>>>>>>>>> directory (we'll call this $JavaHelp) and contains demos, doc, src, >>>>>>>>>> license, etc., actually must point to $JavaHelp/javahelp (which contains >>>>>>>>>> bin and lib). This is not clear on the readme. >>>>>>>>>> - JUnit is NOT optional. jtreg won't "make" without it. >>>>>>>>>> Furthermore, JUNIT_JAR must point to junit.jar (which the readme does not >>>>>>>>>> say). >>>>>>>>>> - TestNG is NOT optional. jtreg won't "make" without it. >>>>>>>>>> Furthermore, TESTNG_HOME must point to a directory containing LICENSE.txt >>>>>>>>>> (which does not exist for TestNG, so I had to invent one) and TESTNG_JAR >>>>>>>>>> must point to testng.jar. The readme doesn't indicate any of this. >>>>>>>>>> - Ant is NOT optional. Unlike usual systems where ANT_HOME >>>>>>>>>> indicates where Ant lives, jtreg requires ANTHOME (which the readme does >>>>>>>>>> not say). >>>>>>>>>> >>>>>>>>>> After this is where I hit the roadblock I cannot overcome: >>>>>>>>>> >>>>>>>>>> There's some thing called "jcov" that is NOT optional. Worse, >>>>>>>>>> jcov, what it is, and where you can find/download it isn't indicated >>>>>>>>>> anywhere on the readme. I spent the last hour scouring Google for jcov. >>>>>>>>>> I've found plenty of references to jcov.jar in JDK source repositories and >>>>>>>>>> mirrors (and apparently it's supposed to contain classes in the >>>>>>>>>> com.sun.tdk.jcov package), but as far as I can tell jcov doesn't exist. I >>>>>>>>>> can't find it anywhere, and jtreg won't "make" without it. If JCOV_HOME >>>>>>>>>> doesn't exist, "make" looks in /java/re/jcov/2.0/promoted/**latest/binaries/jcov_2.0/, >>>>>>>>>> but that certainly doesn't exist, and there's nothing anything like that >>>>>>>>>> underneath the home directories for my JDKs or JREs. >>>>>>>>>> >>>>>>>>>> Can someone help me sort this out and point me to where I can >>>>>>>>>> download jcov? >>>>>>>>>> >>>>>>>>>> And can someone update the readmes? >>>>>>>>>> >>>>>>>>>> Thanks, >>>>>>>>>> >>>>>>>>>> Nick >>>>>>>>>> >>>>>>>>> Nick, >>>>>>>>> >>>>>>>>> I am sorry for your frustration. >>>>>>>>> >>>>>>>>> jcov is a Java Code Coverage tool. As of now, it is not open >>>>>>>>> source, so I will have to update the README and Makefile to ensure that you >>>>>>>>> can build without it. >>>>>>>>> >>>>>>>>> -- Jon >>>>>>>>> >>>>>>>> Okay. How soon do you think you can get that done? I'm on a time >>>>>>>> crunch here and I can't submit this patch without running tests. If there's >>>>>>>> a simple change I can make locally to disable the need for jcov, feel free >>>>>>>> to instruct me. >>>>>>>> >>>>>>>> Thanks, >>>>>>>> >>>>>>>> Nick >>>>>>>> >>>>>>>> The code is written so that you don't need the jcov libraries to >>>>>>> compile jtreg. You just need to fix the Makefiles to comment out where it >>>>>>> is trying to copy the jcov jar file into the final image. >>>>>>> >>>>>>> -- Jon >>>>>>> >>>>>> Indeed. I commented out this in make/Defs.gmk: >>>>>> >>>>>> #ifndef JCOV_HOME >>>>>> # JCOV_HOME = /java/re/jcov/2.0/promoted/**latest/binaries/jcov_2.0/ >>>>>> #endif >>>>>> >>>>>> And this in make/jtreg.gmk: >>>>>> >>>>>> #ifdef JCOV_HOME >>>>>> # >>>>>> #$(JTREG_IMAGEDIR)/lib/jcov.**jar: $(JCOV_HOME)/lib/jcov.jar >>>>>> # $(RM) -f $@ >>>>>> # $(MKDIR) -p $(@D) >>>>>> # $(CP) $< $@ >>>>>> # >>>>>> #$(JTREG_IMAGEDIR)/lib/jcov_**implant.jar: >>>>>> $(JCOV_HOME)/lib/jcov_implant.**jar >>>>>> # $(RM) -f $@ >>>>>> # $(MKDIR) -p $(@D) >>>>>> # $(CP) $< $@ >>>>>> # >>>>>> #TARGETS.ZIP.jtreg += \ >>>>>> # $(JTREG_IMAGEDIR)/lib/jcov.jar \ >>>>>> # $(JTREG_IMAGEDIR)/lib/jcov_**implant.jar >>>>>> # >>>>>> #endif JCOV_HOME >>>>>> >>>>>> And now it builds. Thanks. >>>>>> >>>>>> Nick >>>>>> >>>>> Thanks for the update. So the "broken" part that needs fixing is >>>>> just the first 3 lines you commented out, right? If you just comment those >>>>> lines out, the ifdef in the second block will take care of the rest. >>>>> >>>>> -- Jon >>>>> >>>> You'd think, but just commenting out the first three lines (from >>>> Defs.gmk) didn't work. I had to comment out the second block (jtreg.gmk), >>>> too. Doesn't make any sense to me, but that's what worked. >>>> >>>> Nick >>>> >>> >>> Hmm. OK. Thanks for the info. >>> >>> -- Jon >>> >> If it helps any, originally the error message was something like >> "Required file /java/re/jcov/2.0/promoted/**latest/binaries/jcov_2.0/lib/ >> **jcov.jar not found." When I commented out the three lines the error >> changed to something like "Failed to copy file lib/jcov.jar to >> build/images/jtreg/lib/jcov.**jar." Commenting out the second block got >> rid of the second error. It's almost like JCOV_HOME was getting set to >> blank somehow. >> >> Nick >> >> > Yeah, I'll play around with it, and make sure all the messages make sense > when the various variables are unset. I'll also update the README files. > > -- jon > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.openjdk.java.net/pipermail/jtreg-use/attachments/20131002/43cda806/attachment.html From martinrb at google.com Wed Oct 2 16:15:37 2013 From: martinrb at google.com (Martin Buchholz) Date: Wed, 2 Oct 2013 16:15:37 -0700 Subject: Can't Compile jtreg In-Reply-To: References: <51DF2F1B-5307-49F9-AA0D-C6EAE78B802F@nicholaswilliams.net> <51F7F0C6.60709@oracle.com> <51F7F3C6.4090208@oracle.com> <1422892F-4095-4D10-A2C3-150F7A2DCC03@nicholaswilliams.net> <51F7F7F7.60504@oracle.com> <05BB8850-52EC-40AD-8F5D-B5B411EFE1C8@nicholaswilliams.net> <51F7FA90.4000801@oracle.com> <8345387A-86AF-4ACE-AD1B-724A2007B369@nicholaswilliams.net> <51F7FEC1.4020608@oracle.com> Message-ID: Sigh.... I mean diff --git a/make/jtreg.gmk b/make/jtreg.gmk --- a/make/jtreg.gmk +++ b/make/jtreg.gmk @@ -350,7 +350,7 @@ # # import JCov -#ifdef JCOV_HOME +ifdef JCOV_HOME $(JTREG_IMAGEDIR)/lib/jcov.jar: $(JCOV_HOME)/lib/jcov.jar $(RM) -f $@ @@ -366,7 +366,7 @@ $(JTREG_IMAGEDIR)/lib/jcov.jar \ $(JTREG_IMAGEDIR)/lib/jcov_implant.jar -#endif JCOV_HOME +endif # JCOV_HOME #---------------------------------------------------------------------- # On Wed, Oct 2, 2013 at 3:53 PM, Martin Buchholz wrote: > Hi Jonathan, > > Your fixes to only use JCOV in an Oracle environment didn't quite work for > me. Here's a small patch to fix an obvious little bug, after which I can > build jtreg successfully (it's still not actually easy, with all the > dependencies). > > diff --git a/make/jtreg.gmk b/make/jtreg.gmk > --- a/make/jtreg.gmk > +++ b/make/jtreg.gmk > @@ -350,7 +350,7 @@ > # > # import JCov > > -#ifdef JCOV_HOME > +ifdef JCOV_HOME > > $(JTREG_IMAGEDIR)/lib/jcov.jar: $(JCOV_HOME)/lib/jcov.jar > $(RM) -f $@ > @@ -366,7 +366,7 @@ > $(JTREG_IMAGEDIR)/lib/jcov.jar \ > $(JTREG_IMAGEDIR)/lib/jcov_implant.jar > > -#endif JCOV_HOME > +endif JCOV_HOME > > #---------------------------------------------------------------------- > # > > > > On Tue, Jul 30, 2013 at 10:58 AM, Jonathan Gibbons < > jonathan.gibbons at oracle.com> wrote: > >> On 07/30/2013 10:51 AM, Nick Williams wrote: >> >>> On Jul 30, 2013, at 12:40 PM, Jonathan Gibbons wrote: >>> >>> On 07/30/2013 10:33 AM, Nick Williams wrote: >>>> >>>>> On Jul 30, 2013, at 12:29 PM, Jonathan Gibbons wrote: >>>>> >>>>> On 07/30/2013 10:25 AM, Nick Williams wrote: >>>>>> >>>>>>> On Jul 30, 2013, at 12:11 PM, Jonathan Gibbons wrote: >>>>>>> >>>>>>> On 07/30/2013 10:04 AM, Nick Williams wrote: >>>>>>>> >>>>>>>>> On Jul 30, 2013, at 11:58 AM, Jonathan Gibbons wrote: >>>>>>>>> >>>>>>>>> On 07/30/2013 09:19 AM, Nick Williams wrote: >>>>>>>>>> >>>>>>>>>>> First, please let me say that the build readme at >>>>>>>>>>> http://openjdk.java.net/jtreg/**build.html(and in HG) is sorely lacking. Here's what I've learned on my own so far, >>>>>>>>>>> from analyzing error messages and reading Defs.gmk: >>>>>>>>>>> >>>>>>>>>>> - JAVAHELP_HOME, which usually points to the JavaHelp home >>>>>>>>>>> directory (we'll call this $JavaHelp) and contains demos, doc, src, >>>>>>>>>>> license, etc., actually must point to $JavaHelp/javahelp (which contains >>>>>>>>>>> bin and lib). This is not clear on the readme. >>>>>>>>>>> - JUnit is NOT optional. jtreg won't "make" without it. >>>>>>>>>>> Furthermore, JUNIT_JAR must point to junit.jar (which the readme does not >>>>>>>>>>> say). >>>>>>>>>>> - TestNG is NOT optional. jtreg won't "make" without it. >>>>>>>>>>> Furthermore, TESTNG_HOME must point to a directory containing LICENSE.txt >>>>>>>>>>> (which does not exist for TestNG, so I had to invent one) and TESTNG_JAR >>>>>>>>>>> must point to testng.jar. The readme doesn't indicate any of this. >>>>>>>>>>> - Ant is NOT optional. Unlike usual systems where ANT_HOME >>>>>>>>>>> indicates where Ant lives, jtreg requires ANTHOME (which the readme does >>>>>>>>>>> not say). >>>>>>>>>>> >>>>>>>>>>> After this is where I hit the roadblock I cannot overcome: >>>>>>>>>>> >>>>>>>>>>> There's some thing called "jcov" that is NOT optional. Worse, >>>>>>>>>>> jcov, what it is, and where you can find/download it isn't indicated >>>>>>>>>>> anywhere on the readme. I spent the last hour scouring Google for jcov. >>>>>>>>>>> I've found plenty of references to jcov.jar in JDK source repositories and >>>>>>>>>>> mirrors (and apparently it's supposed to contain classes in the >>>>>>>>>>> com.sun.tdk.jcov package), but as far as I can tell jcov doesn't exist. I >>>>>>>>>>> can't find it anywhere, and jtreg won't "make" without it. If JCOV_HOME >>>>>>>>>>> doesn't exist, "make" looks in /java/re/jcov/2.0/promoted/**latest/binaries/jcov_2.0/, >>>>>>>>>>> but that certainly doesn't exist, and there's nothing anything like that >>>>>>>>>>> underneath the home directories for my JDKs or JREs. >>>>>>>>>>> >>>>>>>>>>> Can someone help me sort this out and point me to where I can >>>>>>>>>>> download jcov? >>>>>>>>>>> >>>>>>>>>>> And can someone update the readmes? >>>>>>>>>>> >>>>>>>>>>> Thanks, >>>>>>>>>>> >>>>>>>>>>> Nick >>>>>>>>>>> >>>>>>>>>> Nick, >>>>>>>>>> >>>>>>>>>> I am sorry for your frustration. >>>>>>>>>> >>>>>>>>>> jcov is a Java Code Coverage tool. As of now, it is not open >>>>>>>>>> source, so I will have to update the README and Makefile to ensure that you >>>>>>>>>> can build without it. >>>>>>>>>> >>>>>>>>>> -- Jon >>>>>>>>>> >>>>>>>>> Okay. How soon do you think you can get that done? I'm on a time >>>>>>>>> crunch here and I can't submit this patch without running tests. If there's >>>>>>>>> a simple change I can make locally to disable the need for jcov, feel free >>>>>>>>> to instruct me. >>>>>>>>> >>>>>>>>> Thanks, >>>>>>>>> >>>>>>>>> Nick >>>>>>>>> >>>>>>>>> The code is written so that you don't need the jcov libraries to >>>>>>>> compile jtreg. You just need to fix the Makefiles to comment out where it >>>>>>>> is trying to copy the jcov jar file into the final image. >>>>>>>> >>>>>>>> -- Jon >>>>>>>> >>>>>>> Indeed. I commented out this in make/Defs.gmk: >>>>>>> >>>>>>> #ifndef JCOV_HOME >>>>>>> # JCOV_HOME = /java/re/jcov/2.0/promoted/** >>>>>>> latest/binaries/jcov_2.0/ >>>>>>> #endif >>>>>>> >>>>>>> And this in make/jtreg.gmk: >>>>>>> >>>>>>> #ifdef JCOV_HOME >>>>>>> # >>>>>>> #$(JTREG_IMAGEDIR)/lib/jcov.**jar: $(JCOV_HOME)/lib/jcov.jar >>>>>>> # $(RM) -f $@ >>>>>>> # $(MKDIR) -p $(@D) >>>>>>> # $(CP) $< $@ >>>>>>> # >>>>>>> #$(JTREG_IMAGEDIR)/lib/jcov_**implant.jar: >>>>>>> $(JCOV_HOME)/lib/jcov_implant.**jar >>>>>>> # $(RM) -f $@ >>>>>>> # $(MKDIR) -p $(@D) >>>>>>> # $(CP) $< $@ >>>>>>> # >>>>>>> #TARGETS.ZIP.jtreg += \ >>>>>>> # $(JTREG_IMAGEDIR)/lib/jcov.jar \ >>>>>>> # $(JTREG_IMAGEDIR)/lib/jcov_**implant.jar >>>>>>> # >>>>>>> #endif JCOV_HOME >>>>>>> >>>>>>> And now it builds. Thanks. >>>>>>> >>>>>>> Nick >>>>>>> >>>>>> Thanks for the update. So the "broken" part that needs fixing is >>>>>> just the first 3 lines you commented out, right? If you just comment those >>>>>> lines out, the ifdef in the second block will take care of the rest. >>>>>> >>>>>> -- Jon >>>>>> >>>>> You'd think, but just commenting out the first three lines (from >>>>> Defs.gmk) didn't work. I had to comment out the second block (jtreg.gmk), >>>>> too. Doesn't make any sense to me, but that's what worked. >>>>> >>>>> Nick >>>>> >>>> >>>> Hmm. OK. Thanks for the info. >>>> >>>> -- Jon >>>> >>> If it helps any, originally the error message was something like >>> "Required file /java/re/jcov/2.0/promoted/** >>> latest/binaries/jcov_2.0/lib/**jcov.jar not found." When I commented >>> out the three lines the error changed to something like "Failed to copy >>> file lib/jcov.jar to build/images/jtreg/lib/jcov.**jar." Commenting out >>> the second block got rid of the second error. It's almost like JCOV_HOME >>> was getting set to blank somehow. >>> >>> Nick >>> >>> >> Yeah, I'll play around with it, and make sure all the messages make sense >> when the various variables are unset. I'll also update the README files. >> >> -- jon >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.openjdk.java.net/pipermail/jtreg-use/attachments/20131002/3e0feb85/attachment-0001.html From peter.brunet at oracle.com Wed Oct 2 21:42:28 2013 From: peter.brunet at oracle.com (Pete Brunet) Date: Wed, 02 Oct 2013 23:42:28 -0500 Subject: building jtreg - problem with xalan Message-ID: <524CF5B4.4050108@oracle.com> Hi, I need to run an existing regression test to investigate a problem so need to set up jtreg. I'm using cygwin on Win 7. Following is info on my current roadblock. Does anyone have an idea of what is wrong? -Pete /bin/mkdir -p ../build/images/jtreg/doc/jtreg CLASSPATH=/cygdrive/c/Users/Pete/JDK8/xalan-j_2_7_1/xalan.jar:/cygdrive/c/Users/Pete/JDK8/xalan-j_2_7_1/serializer.jar:/cygdrive/c/Users/Pete/JDK8/xalan-j_2_7_1/xml-apis.jar:/cygdrive/c/Users/Pete/JDK8/xalan-j_2_7_1/xercesImpl.jar /cygdrive/c/Program\ Files/Java/jdk1.7.0_25/bin/java org.apache.xalan.xslt.Process -in ../src/share/doc/javatest/regtest/faq.xml \ -xsl ../src/share/doc/javatest/regtest/faqtohtml.xsl \ -out ../build/images/jtreg/doc/jtreg/faq.html \ -param context openjdk Error: Could not find or load main class org.apache.xalan.xslt.Process jtreg.gmk:227: recipe for target `../build/images/jtreg/doc/jtreg/faq.html' failed make: *** [../build/images/jtreg/doc/jtreg/faq.html] Error 1 make: Leaving directory `/cygdrive/c/Users/Pete/JDK8/jtreg/make' org.apache.xalan.xslt.Process /is/ in /cygdrive/c/Users/Pete/JDK8/xalan-j_2_7_1/xalan.jar Here's my script: JDK15HOME='/cygdrive/c/Program\ Files/Java/jdk1.7.0_25' JDK16HOME='/cygdrive/c/Program\ Files/Java/jdk1.7.0_25' JAVAHELP_HOME='/cygdrive/c/Users/Pete/JDK8/jh2.0/javahelp' JTHARNESS_HOME='/cygdrive/c/Users/Pete/JDK8/jtharness' ANTHOME='/cygdrive/c/Program\ Files\ \(x86\)/apache-ant-1.9.1' XALANHOME='/cygdrive/c/Users/Pete/JDK8/xalan-j_2_7_1' JUNIT_JAR='/cygdrive/c/Users/Pete/JDK8/junit/junit.jar' TESTNG_JAR='/cygdrive/c/Users/Pete/JDK8/testng/testng-6.8.7.jar' export JDK15HOME export JDK16HOME export JAVAHELP_HOME export JTHARNESS_HOME export ANTHOME export XALANHOME export JUNIT_JAR export TESTNG_JAR make -C make From martinrb at google.com Wed Oct 2 21:53:39 2013 From: martinrb at google.com (Martin Buchholz) Date: Wed, 2 Oct 2013 21:53:39 -0700 Subject: building jtreg - problem with xalan In-Reply-To: <524CF5B4.4050108@oracle.com> References: <524CF5B4.4050108@oracle.com> Message-ID: I had success building today. Do you have the 2-jar or the 1-jar distribution of xalan-j? The 1-jar distribution worked well for me (on Linux). See: http://xml.apache.org/xalan-j/downloads.html On Wed, Oct 2, 2013 at 9:42 PM, Pete Brunet wrote: > Hi, I need to run an existing regression test to investigate a problem > so need to set up jtreg. I'm using cygwin on Win 7. Following is info > on my current roadblock. Does anyone have an idea of what is wrong? -Pete > > > /bin/mkdir -p ../build/images/jtreg/doc/jtreg > > CLASSPATH=/cygdrive/c/Users/Pete/JDK8/xalan-j_2_7_1/xalan.jar:/cygdrive/c/Users/Pete/JDK8/xalan-j_2_7_1/serializer.jar:/cygdrive/c/Users/Pete/JDK8/xalan-j_2_7_1/xml-apis.jar:/cygdrive/c/Users/Pete/JDK8/xalan-j_2_7_1/xercesImpl.jar > /cygdrive/c/Program\ Files/Java/jdk1.7.0_25/bin/java > org.apache.xalan.xslt.Process -in > ../src/share/doc/javatest/regtest/faq.xml \ > -xsl ../src/share/doc/javatest/regtest/faqtohtml.xsl \ > -out ../build/images/jtreg/doc/jtreg/faq.html \ > -param context openjdk > Error: Could not find or load main class org.apache.xalan.xslt.Process > jtreg.gmk:227: recipe for target > `../build/images/jtreg/doc/jtreg/faq.html' failed > make: *** [../build/images/jtreg/doc/jtreg/faq.html] Error 1 > make: Leaving directory `/cygdrive/c/Users/Pete/JDK8/jtreg/make' > > org.apache.xalan.xslt.Process /is/ in > /cygdrive/c/Users/Pete/JDK8/xalan-j_2_7_1/xalan.jar > > Here's my script: > > JDK15HOME='/cygdrive/c/Program\ Files/Java/jdk1.7.0_25' > JDK16HOME='/cygdrive/c/Program\ Files/Java/jdk1.7.0_25' > JAVAHELP_HOME='/cygdrive/c/Users/Pete/JDK8/jh2.0/javahelp' > JTHARNESS_HOME='/cygdrive/c/Users/Pete/JDK8/jtharness' > ANTHOME='/cygdrive/c/Program\ Files\ \(x86\)/apache-ant-1.9.1' > XALANHOME='/cygdrive/c/Users/Pete/JDK8/xalan-j_2_7_1' > JUNIT_JAR='/cygdrive/c/Users/Pete/JDK8/junit/junit.jar' > TESTNG_JAR='/cygdrive/c/Users/Pete/JDK8/testng/testng-6.8.7.jar' > > export JDK15HOME > export JDK16HOME > export JAVAHELP_HOME > export JTHARNESS_HOME > export ANTHOME > export XALANHOME > export JUNIT_JAR > export TESTNG_JAR > > make -C make > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.openjdk.java.net/pipermail/jtreg-use/attachments/20131002/dd852de8/attachment.html From peter.brunet at oracle.com Thu Oct 3 06:35:29 2013 From: peter.brunet at oracle.com (Pete Brunet) Date: Thu, 03 Oct 2013 08:35:29 -0500 Subject: building jtreg - problem with xalan In-Reply-To: References: <524CF5B4.4050108@oracle.com> Message-ID: <524D72A1.8020304@oracle.com> Hi Martin, I used the 1 jar version (on Win 7). (I assume this is the first option of the two listed on that page.) -Pete On 10/2/13 11:53 PM, Martin Buchholz wrote: > I had success building today. > Do you have the 2-jar or the 1-jar distribution of xalan-j? > The 1-jar distribution worked well for me (on Linux). > See: http://xml.apache.org/xalan-j/downloads.html > > > On Wed, Oct 2, 2013 at 9:42 PM, Pete Brunet > wrote: > > Hi, I need to run an existing regression test to investigate a problem > so need to set up jtreg. I'm using cygwin on Win 7. Following is > info > on my current roadblock. Does anyone have an idea of what is > wrong? -Pete > > > /bin/mkdir -p ../build/images/jtreg/doc/jtreg > CLASSPATH=/cygdrive/c/Users/Pete/JDK8/xalan-j_2_7_1/xalan.jar:/cygdrive/c/Users/Pete/JDK8/xalan-j_2_7_1/serializer.jar:/cygdrive/c/Users/Pete/JDK8/xalan-j_2_7_1/xml-apis.jar:/cygdrive/c/Users/Pete/JDK8/xalan-j_2_7_1/xercesImpl.jar > /cygdrive/c/Program\ Files/Java/jdk1.7.0_25/bin/java > org.apache.xalan.xslt.Process -in > ../src/share/doc/javatest/regtest/faq.xml \ > -xsl ../src/share/doc/javatest/regtest/faqtohtml.xsl \ > -out ../build/images/jtreg/doc/jtreg/faq.html \ > -param context openjdk > Error: Could not find or load main class org.apache.xalan.xslt.Process > jtreg.gmk:227: recipe for target > `../build/images/jtreg/doc/jtreg/faq.html' failed > make: *** [../build/images/jtreg/doc/jtreg/faq.html] Error 1 > make: Leaving directory `/cygdrive/c/Users/Pete/JDK8/jtreg/make' > > org.apache.xalan.xslt.Process /is/ in > /cygdrive/c/Users/Pete/JDK8/xalan-j_2_7_1/xalan.jar > > Here's my script: > > JDK15HOME='/cygdrive/c/Program\ Files/Java/jdk1.7.0_25' > JDK16HOME='/cygdrive/c/Program\ Files/Java/jdk1.7.0_25' > JAVAHELP_HOME='/cygdrive/c/Users/Pete/JDK8/jh2.0/javahelp' > JTHARNESS_HOME='/cygdrive/c/Users/Pete/JDK8/jtharness' > ANTHOME='/cygdrive/c/Program\ Files\ \(x86\)/apache-ant-1.9.1' > XALANHOME='/cygdrive/c/Users/Pete/JDK8/xalan-j_2_7_1' > JUNIT_JAR='/cygdrive/c/Users/Pete/JDK8/junit/junit.jar' > TESTNG_JAR='/cygdrive/c/Users/Pete/JDK8/testng/testng-6.8.7.jar' > > export JDK15HOME > export JDK16HOME > export JAVAHELP_HOME > export JTHARNESS_HOME > export ANTHOME > export XALANHOME > export JUNIT_JAR > export TESTNG_JAR > > make -C make > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.openjdk.java.net/pipermail/jtreg-use/attachments/20131003/5ab53438/attachment.html From omajid at redhat.com Thu Oct 3 07:47:52 2013 From: omajid at redhat.com (Omair Majid) Date: Thu, 03 Oct 2013 10:47:52 -0400 Subject: Can't Compile jtreg In-Reply-To: References: <51DF2F1B-5307-49F9-AA0D-C6EAE78B802F@nicholaswilliams.net> <51F7F0C6.60709@oracle.com> <51F7F3C6.4090208@oracle.com> <1422892F-4095-4D10-A2C3-150F7A2DCC03@nicholaswilliams.net> <51F7F7F7.60504@oracle.com> <05BB8850-52EC-40AD-8F5D-B5B411EFE1C8@nicholaswilliams.net> <51F7FA90.4000801@oracle.com> <8345387A-86AF-4ACE-AD1B-724A2007B369@nicholaswilliams.net> <51F7FEC1.4020608@oracle.com> Message-ID: <524D8398.6060807@redhat.com> On 10/02/2013 07:15 PM, Martin Buchholz wrote: > Sigh.... I mean > > diff --git a/make/jtreg.gmk b/make/jtreg.gmk > --- a/make/jtreg.gmk > +++ b/make/jtreg.gmk > @@ -350,7 +350,7 @@ > # > # import JCov > > -#ifdef JCOV_HOME > +ifdef JCOV_HOME > > $(JTREG_IMAGEDIR)/lib/jcov.jar: $(JCOV_HOME)/lib/jcov.jar > $(RM) -f $@ > @@ -366,7 +366,7 @@ > $(JTREG_IMAGEDIR)/lib/jcov.jar \ > $(JTREG_IMAGEDIR)/lib/jcov_implant.jar > > -#endif JCOV_HOME > +endif # JCOV_HOME > I was trying to build jtreg yesterday and this is pretty much what I ended up doing too. The built jtreg seems functional so far. Cheers, Omair -- PGP Key: 66484681 (http://pgp.mit.edu/) Fingerprint = F072 555B 0A17 3957 4E95 0056 F286 F14F 6648 4681 From jonathan.gibbons at oracle.com Thu Oct 3 07:55:29 2013 From: jonathan.gibbons at oracle.com (Jonathan Gibbons) Date: Thu, 03 Oct 2013 07:55:29 -0700 Subject: Can't Compile jtreg In-Reply-To: References: <51DF2F1B-5307-49F9-AA0D-C6EAE78B802F@nicholaswilliams.net> <51F7F0C6.60709@oracle.com> <51F7F3C6.4090208@oracle.com> <1422892F-4095-4D10-A2C3-150F7A2DCC03@nicholaswilliams.net> <51F7F7F7.60504@oracle.com> <05BB8850-52EC-40AD-8F5D-B5B411EFE1C8@nicholaswilliams.net> <51F7FA90.4000801@oracle.com> <8345387A-86AF-4ACE-AD1B-724A2007B369@nicholaswilliams.net> <51F7FEC1.4020608@oracle.com> Message-ID: <524D8561.1060907@oracle.com> Martin, Thanks. It is on my list to make it easier to build jtreg, and I will include your fix. -- Jon On 10/02/2013 03:53 PM, Martin Buchholz wrote: > Hi Jonathan, > > Your fixes to only use JCOV in an Oracle environment didn't quite work > for me. Here's a small patch to fix an obvious little bug, after > which I can build jtreg successfully (it's still not actually easy, > with all the dependencies). > > diff --git a/make/jtreg.gmk b/make/jtreg.gmk > --- a/make/jtreg.gmk > +++ b/make/jtreg.gmk > @@ -350,7 +350,7 @@ > # > # import JCov > -#ifdef JCOV_HOME > +ifdef JCOV_HOME > $(JTREG_IMAGEDIR)/lib/jcov.jar: $(JCOV_HOME)/lib/jcov.jar > $(RM) -f $@ > @@ -366,7 +366,7 @@ > $(JTREG_IMAGEDIR)/lib/jcov.jar \ > $(JTREG_IMAGEDIR)/lib/jcov_implant.jar > -#endif JCOV_HOME > +endif JCOV_HOME > #---------------------------------------------------------------------- > # > > > > On Tue, Jul 30, 2013 at 10:58 AM, Jonathan Gibbons > > wrote: > > On 07/30/2013 10:51 AM, Nick Williams wrote: > > On Jul 30, 2013, at 12:40 PM, Jonathan Gibbons wrote: > > On 07/30/2013 10:33 AM, Nick Williams wrote: > > On Jul 30, 2013, at 12:29 PM, Jonathan Gibbons wrote: > > On 07/30/2013 10:25 AM, Nick Williams wrote: > > On Jul 30, 2013, at 12:11 PM, Jonathan Gibbons > wrote: > > On 07/30/2013 10:04 AM, Nick Williams wrote: > > On Jul 30, 2013, at 11:58 AM, Jonathan > Gibbons wrote: > > On 07/30/2013 09:19 AM, Nick > Williams wrote: > > First, please let me say that > the build readme at > http://openjdk.java.net/jtreg/build.html > (and in HG) is sorely lacking. > Here's what I've learned on my > own so far, from analyzing > error messages and reading > Defs.gmk: > > - JAVAHELP_HOME, which usually > points to the JavaHelp home > directory (we'll call this > $JavaHelp) and contains demos, > doc, src, license, etc., > actually must point to > $JavaHelp/javahelp (which > contains bin and lib). This is > not clear on the readme. > - JUnit is NOT optional. jtreg > won't "make" without it. > Furthermore, JUNIT_JAR must > point to junit.jar (which the > readme does not say). > - TestNG is NOT optional. > jtreg won't "make" without it. > Furthermore, TESTNG_HOME must > point to a directory > containing LICENSE.txt (which > does not exist for TestNG, so > I had to invent one) and > TESTNG_JAR must point to > testng.jar. The readme doesn't > indicate any of this. > - Ant is NOT optional. Unlike > usual systems where ANT_HOME > indicates where Ant lives, > jtreg requires ANTHOME (which > the readme does not say). > > After this is where I hit the > roadblock I cannot overcome: > > There's some thing called > "jcov" that is NOT optional. > Worse, jcov, what it is, and > where you can find/download it > isn't indicated anywhere on > the readme. I spent the last > hour scouring Google for jcov. > I've found plenty of > references to jcov.jar in JDK > source repositories and > mirrors (and apparently it's > supposed to contain classes in > the com.sun.tdk.jcov package), > but as far as I can tell jcov > doesn't exist. I can't find it > anywhere, and jtreg won't > "make" without it. If > JCOV_HOME doesn't exist, > "make" looks in > /java/re/jcov/2.0/promoted/latest/binaries/jcov_2.0/, > but that certainly doesn't > exist, and there's nothing > anything like that underneath > the home directories for my > JDKs or JREs. > > Can someone help me sort this > out and point me to where I > can download jcov? > > And can someone update the > readmes? > > Thanks, > > Nick > > Nick, > > I am sorry for your frustration. > > jcov is a Java Code Coverage tool. > As of now, it is not open source, > so I will have to update the > README and Makefile to ensure that > you can build without it. > > -- Jon > > Okay. How soon do you think you can > get that done? I'm on a time crunch > here and I can't submit this patch > without running tests. If there's a > simple change I can make locally to > disable the need for jcov, feel free > to instruct me. > > Thanks, > > Nick > > The code is written so that you don't need > the jcov libraries to compile jtreg. You > just need to fix the Makefiles to comment > out where it is trying to copy the jcov > jar file into the final image. > > -- Jon > > Indeed. I commented out this in make/Defs.gmk: > > #ifndef JCOV_HOME > # JCOV_HOME = > /java/re/jcov/2.0/promoted/latest/binaries/jcov_2.0/ > #endif > > And this in make/jtreg.gmk: > > #ifdef JCOV_HOME > # > #$(JTREG_IMAGEDIR)/lib/jcov.jar: > $(JCOV_HOME)/lib/jcov.jar > # $(RM) -f $@ > # $(MKDIR) -p $(@D) > # $(CP) $< $@ > # > #$(JTREG_IMAGEDIR)/lib/jcov_implant.jar: > $(JCOV_HOME)/lib/jcov_implant.jar > # $(RM) -f $@ > # $(MKDIR) -p $(@D) > # $(CP) $< $@ > # > #TARGETS.ZIP.jtreg += \ > # $(JTREG_IMAGEDIR)/lib/jcov.jar \ > # $(JTREG_IMAGEDIR)/lib/jcov_implant.jar > # > #endif JCOV_HOME > > And now it builds. Thanks. > > Nick > > Thanks for the update. So the "broken" part that > needs fixing is just the first 3 lines you > commented out, right? If you just comment those > lines out, the ifdef in the second block will take > care of the rest. > > -- Jon > > You'd think, but just commenting out the first three > lines (from Defs.gmk) didn't work. I had to comment > out the second block (jtreg.gmk), too. Doesn't make > any sense to me, but that's what worked. > > Nick > > > Hmm. OK. Thanks for the info. > > -- Jon > > If it helps any, originally the error message was something > like "Required file > /java/re/jcov/2.0/promoted/latest/binaries/jcov_2.0/lib/jcov.jar > not found." When I commented out the three lines the error > changed to something like "Failed to copy file lib/jcov.jar to > build/images/jtreg/lib/jcov.jar." Commenting out the second > block got rid of the second error. It's almost like JCOV_HOME > was getting set to blank somehow. > > Nick > > > Yeah, I'll play around with it, and make sure all the messages > make sense when the various variables are unset. I'll also update > the README files. > > -- jon > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.openjdk.java.net/pipermail/jtreg-use/attachments/20131003/f116b610/attachment-0001.html From omajid at redhat.com Thu Oct 3 08:35:40 2013 From: omajid at redhat.com (Omair Majid) Date: Thu, 03 Oct 2013 11:35:40 -0400 Subject: building jtreg - problem with xalan In-Reply-To: <524CF5B4.4050108@oracle.com> References: <524CF5B4.4050108@oracle.com> Message-ID: <524D8ECC.5000407@redhat.com> Hi Pete, On 10/03/2013 12:42 AM, Pete Brunet wrote: > Hi, I need to run an existing regression test to investigate a problem > so need to set up jtreg. I'm using cygwin on Win 7. Following is info > on my current roadblock. Does anyone have an idea of what is wrong? -Pete My setup is a little different, but hopefully this will help. > CLASSPATH=/cygdrive/c/Users/Pete/JDK8/xalan-j_2_7_1/xalan.jar:/cygdrive/c/Users/Pete/JDK8/xalan-j_2_7_1/serializer.jar:/cygdrive/c/Users/Pete/JDK8/xalan-j_2_7_1/xml-apis.jar:/cygdrive/c/Users/Pete/JDK8/xalan-j_2_7_1/xercesImpl.jar > /cygdrive/c/Program\ Files/Java/jdk1.7.0_25/bin/java So this CLASSPATH is where the build is searching for xalan. Is your xalan jar located at /cygdrive/c/Users/Pete/JDK8/xalan-j_2_7_1/xalan.jar ? If not, you may have to set XALANHOME to point to where the xalan.jar is located, or edit the make/jtreg.gmk file and fix the line that says: XALAN_PATH = $(XALANHOME)/xalan.jar:$(XALANHOME)/serializer.jar:$(XALANHOME)/xml-apis.jar:$(XALANHOME)/xercesImpl.jar I just had to modify it to point to my xalan (2) jar and xalan (2) serializer jar. > XALANHOME='/cygdrive/c/Users/Pete/JDK8/xalan-j_2_7_1' xalan-j-2.* is xalan 2. The jar might be named xalan-j2.jar or something. You may want to specify a XALAN_PATH directly or edit the makefile. Cheers, Omair -- PGP Key: 66484681 (http://pgp.mit.edu/) Fingerprint = F072 555B 0A17 3957 4E95 0056 F286 F14F 6648 4681 From omajid at redhat.com Thu Oct 3 08:47:17 2013 From: omajid at redhat.com (Omair Majid) Date: Thu, 03 Oct 2013 11:47:17 -0400 Subject: Can't Compile jtreg In-Reply-To: <524D8561.1060907@oracle.com> References: <51DF2F1B-5307-49F9-AA0D-C6EAE78B802F@nicholaswilliams.net> <51F7F0C6.60709@oracle.com> <51F7F3C6.4090208@oracle.com> <1422892F-4095-4D10-A2C3-150F7A2DCC03@nicholaswilliams.net> <51F7F7F7.60504@oracle.com> <05BB8850-52EC-40AD-8F5D-B5B411EFE1C8@nicholaswilliams.net> <51F7FA90.4000801@oracle.com> <8345387A-86AF-4ACE-AD1B-724A2007B369@nicholaswilliams.net> <51F7FEC1.4020608@oracle.com> <524D8561.1060907@oracle.com> Message-ID: <524D9185.8010208@redhat.com> Hi Jonathan, On 10/03/2013 10:55 AM, Jonathan Gibbons wrote: > Thanks. It is on my list to make it easier to build jtreg, and I will > include your fix. I was building jtreg using java 7, and ran into a few issues where -target was specified but no -source and javac complains: javac: target release 1.5 conflicts with default source release 1.7 This patch fixed things for me: http://cr.openjdk.java.net/~omajid/webrevs/jtreg-explicit-source-level.patch Cheers, Omair -- PGP Key: 66484681 (http://pgp.mit.edu/) Fingerprint = F072 555B 0A17 3957 4E95 0056 F286 F14F 6648 4681 From peter.brunet at oracle.com Thu Oct 3 08:51:30 2013 From: peter.brunet at oracle.com (Pete Brunet) Date: Thu, 03 Oct 2013 10:51:30 -0500 Subject: building jtreg - problem with xalan In-Reply-To: <524D8ECC.5000407@redhat.com> References: <524CF5B4.4050108@oracle.com> <524D8ECC.5000407@redhat.com> Message-ID: <524D9282.9020402@oracle.com> Hi Omair, On 10/3/13 10:35 AM, Omair Majid wrote: > Hi Pete, > > On 10/03/2013 12:42 AM, Pete Brunet wrote: >> Hi, I need to run an existing regression test to investigate a problem >> so need to set up jtreg. I'm using cygwin on Win 7. Following is info >> on my current roadblock. Does anyone have an idea of what is wrong? -Pete > My setup is a little different, but hopefully this will help. > >> CLASSPATH=/cygdrive/c/Users/Pete/JDK8/xalan-j_2_7_1/xalan.jar:/cygdrive/c/Users/Pete/JDK8/xalan-j_2_7_1/serializer.jar:/cygdrive/c/Users/Pete/JDK8/xalan-j_2_7_1/xml-apis.jar:/cygdrive/c/Users/Pete/JDK8/xalan-j_2_7_1/xercesImpl.jar >> /cygdrive/c/Program\ Files/Java/jdk1.7.0_25/bin/java > So this CLASSPATH is where the build is searching for xalan. Is your > xalan jar located at /cygdrive/c/Users/Pete/JDK8/xalan-j_2_7_1/xalan.jar > ? Yes it is. > If not, you may have to set XALANHOME to point to where the xalan.jar > is located, I have XALANHOME='/cygdrive/c/Users/Pete/JDK8/xalan-j_2_7_1' export XALANHOME > or edit the make/jtreg.gmk file and fix the line that says: > XALAN_PATH = > $(XALANHOME)/xalan.jar:$(XALANHOME)/serializer.jar:$(XALANHOME)/xml-apis.jar:$(XALANHOME)/xercesImpl.jar > > I just had to modify it to point to my xalan (2) jar and xalan (2) > serializer jar. > >> XALANHOME='/cygdrive/c/Users/Pete/JDK8/xalan-j_2_7_1' > xalan-j-2.* is xalan 2. The jar might be named xalan-j2.jar or > something. It's named correctly, i.e. xalan.jar - also that directory has serializer.jar > You may want to specify a XALAN_PATH directly or edit the > makefile. > > Cheers, > Omair I wonder if the problem has anything to do with the cygwin style path. Pete From jonathan.gibbons at oracle.com Fri Oct 11 15:20:30 2013 From: jonathan.gibbons at oracle.com (Jonathan Gibbons) Date: Fri, 11 Oct 2013 15:20:30 -0700 Subject: Running OpenJDK regression tests with 'jtreg -gui' fails In-Reply-To: References: <524B7FAD.3050400@oracle.com> Message-ID: <525879AE.4090807@oracle.com> On 10/02/2013 02:46 AM, Volker Simonis wrote: > So this is really all quite confusing! I would suggest to update the > OpenJDK jtreg build page athttp://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 fromhttp://download.java.net/openjdk/jtreg > > Thanks for your support and best regards, > Volker I'm pleased you got this sorted out, and I'm sorry for the confusion. We used to provide be able to provide a dowload link for the latest version, and maybe because of that, the build instructions suffered more bitrot than one would like. Unfortunately, we (Oracle) can no longer provide a download link, and so I will make more of an effort to keep the build instructions up to date. For what it's worth, for anyone working on tests in the jdk8/ forests, I would encourage the use of the latest jtreg source code, because of the new features going in that are now being relied on. -- Jon From weijun.wang at oracle.com Sat Oct 12 02:37:31 2013 From: weijun.wang at oracle.com (Weijun Wang) Date: Sat, 12 Oct 2013 17:37:31 +0800 Subject: Multiple action using same scratch in a single test? Message-ID: <5259185B.3060403@oracle.com> If I have multiple @run in a single test, I guess they will use the same scratch directory and the files generated by the first @run will be observable by the others. Please confirm. Thanks Max From christian.tornqvist at oracle.com Sat Oct 12 04:12:24 2013 From: christian.tornqvist at oracle.com (Christian Tornqvist) Date: Sat, 12 Oct 2013 07:12:24 -0400 Subject: Multiple action using same scratch in a single test? In-Reply-To: <5259185B.3060403@oracle.com> References: <5259185B.3060403@oracle.com> Message-ID: <66C2AAB8-4D22-4D2E-8173-325C44837E6E@oracle.com> Hi Max, Yes, they'll be able to see the files created by previous @run tasks. Thanks, Christian On Oct 12, 2013, at 5:37, Weijun Wang wrote: > If I have multiple @run in a single test, I guess they will use the same scratch directory and the files generated by the first @run will be observable by the others. Please confirm. > > Thanks > Max From francis.andre.kampbell at orange.fr Thu Oct 17 20:50:09 2013 From: francis.andre.kampbell at orange.fr (Francis ANDRE) Date: Fri, 18 Oct 2013 05:50:09 +0200 Subject: building jtreg - problem with xalan Message-ID: <5260AFF1.8040608@orange.fr> Hi Pete. The problem is caused by the ':' in the classpath. While under a cygwin platform, java is always a "windows" product that should understand drive letter. So java is using the windows path separator ';'. So all *.gmk classpath computation should be made with ';' as path separator on cygwin and ':' on non cygwin platform. HTH Francis Pete Brunet writes: > > Hi, I need to run an existing regression test to investigate a problem > so need to set up jtreg. I'm using cygwin on Win 7. Following is info > on my current roadblock. Does anyone have an idea of what is wrong? -Pete > > > /bin/mkdir -p ../build/images/jtreg/doc/jtreg > CLASSPATH=/cygdrive/c/Users/Pete/JDK8/xalan-j_2_7_1/xalan.jar:/cygdrive/c/Users/Pete/JDK8/xalan-j_2_7_1/serializer.jar:/cygdrive/c/Users/Pete/JDK8/xalan-j_2_7_1/xml-apis.jar:/cygdrive/c/Users/Pete/JDK8/xalan-j_2_7_1/xercesImpl.jar > /cygdrive/c/Program\ Files/Java/jdk1.7.0_25/bin/java > org.apache.xalan.xslt.Process -in > ../src/share/doc/javatest/regtest/faq.xml \ > -xsl ../src/share/doc/javatest/regtest/faqtohtml.xsl \ > -out ../build/images/jtreg/doc/jtreg/faq.html \ > -param context openjdk > Error: Could not find or load main class org.apache.xalan.xslt.Process > jtreg.gmk:227: recipe for target > `../build/images/jtreg/doc/jtreg/faq.html' failed > make: *** [../build/images/jtreg/doc/jtreg/faq.html] Error 1 > make: Leaving directory `/cygdrive/c/Users/Pete/JDK8/jtreg/make' > > org.apache.xalan.xslt.Process /is/ in > /cygdrive/c/Users/Pete/JDK8/xalan-j_2_7_1/xalan.jar > > Here's my script: > > JDK15HOME='/cygdrive/c/Program\ Files/Java/jdk1.7.0_25' > JDK16HOME='/cygdrive/c/Program\ Files/Java/jdk1.7.0_25' > JAVAHELP_HOME='/cygdrive/c/Users/Pete/JDK8/jh2.0/javahelp' > JTHARNESS_HOME='/cygdrive/c/Users/Pete/JDK8/jtharness' > ANTHOME='/cygdrive/c/Program\ Files\ \(x86\)/apache-ant-1.9.1' > XALANHOME='/cygdrive/c/Users/Pete/JDK8/xalan-j_2_7_1' > JUNIT_JAR='/cygdrive/c/Users/Pete/JDK8/junit/junit.jar' > TESTNG_JAR='/cygdrive/c/Users/Pete/JDK8/testng/testng-6.8.7.jar' > > export JDK15HOME > export JDK16HOME > export JAVAHELP_HOME > export JTHARNESS_HOME > export ANTHOME > export XALANHOME > export JUNIT_JAR > export TESTNG_JAR > > make -C make > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.openjdk.java.net/pipermail/jtreg-use/attachments/20131018/91a327b3/attachment.html From francis.andre.kampbell at orange.fr Thu Oct 17 21:01:48 2013 From: francis.andre.kampbell at orange.fr (Francis ANDRE) Date: Fri, 18 Oct 2013 06:01:48 +0200 Subject: RFR: patch for building jtreg on WXP/W7 Message-ID: <5260B2AC.8070006@orange.fr> HI I made a series of patches for building jtreg on WXP/W7 with cygwin. Patches are produced using the webrev.ksh tool. Is somebody interested in getting those patches or review them? Francis Here my sanity check: FrancisANDRE at idefix /cygdrive/Z/JDK/jtreg $ make -C make sanity /bin/sh: C:/: is a directory which: no linklint in (/usr/local/bin:/usr/bin:/cygdrive/c/WINDOWS:/cygdrive/c/WINDOWS/system32:/cyg drive/c/WINDOWS/System32/Wbem:/cygdrive/c/Program Files/Microsoft Visual Studio 10.0/Common7/IDE:/cy gdrive/c/Program Files/Microsoft Visual Studio 10.0/VC/BIN:/cygdrive/c/Program Files/Microsoft Visua l Studio 10.0/Common7/Tools:/cygdrive/c/WINDOWS/Microsoft.NET/Framework/v4.0.30319:/cygdrive/c/Progr am Files/Microsoft Visual Studio 10.0/VC/VCPackages:/cygdrive/c/Program Files/Microsoft SDKs/Windows /v7.0A/bin/NETFX 4.0 Tools:/cygdrive/c/Program Files/Microsoft SDKs/Windows/v7.0A/bin:/cygdrive/c/Pr ogram Files/Apache Software Foundation/apache-ant-1.8.4/bin:/cygdrive/c/Program Files/Apache Softwar e Foundation/apache-maven-3.0.3/bin) make: Entering directory `/cygdrive/Z/JDK/jtreg/make' JDK15HOME = C:/Progra~1/Java/jdk1.6.0_35 JDK16HOME = C:/Progra~1/Java/jdk1.6.0_35 JAVAHELP_HOME = Z:/JDK/javahelp/2.0/javahelp JAVATEST_HOME = Z:/JDK/jtharness ANTHOME = C:/Progra~1/Apache~2/apache-ant-1.8.4 XALANHOME = C:/Progra~1/Apache~2/xalan-j_2_7_1 JUNIT_JAR = Z:/JDK/junit/4.8.2/junit-4.8.2.jar LINKLINT = make: Leaving directory `/cygdrive/Z/JDK/jtreg/make' From jonathan.gibbons at oracle.com Thu Oct 17 21:27:17 2013 From: jonathan.gibbons at oracle.com (Jonathan Gibbons) Date: Thu, 17 Oct 2013 21:27:17 -0700 Subject: RFR: patch for building jtreg on WXP/W7 In-Reply-To: <5260B2AC.8070006@orange.fr> References: <5260B2AC.8070006@orange.fr> Message-ID: <5260B8A5.5070600@oracle.com> Francis, I would be interested to see the patches, if you would like to contribute them back to the main jtreg repo. For info on making contributions to OpenJDK, see http://openjdk.java.net/contribute/ -- Jon On 10/17/2013 09:01 PM, Francis ANDRE wrote: > HI > > I made a series of patches for building jtreg on WXP/W7 with cygwin. > Patches are produced using the webrev.ksh tool. Is somebody interested > in getting those patches or review them? > > Francis > > Here my sanity check: > > FrancisANDRE at idefix /cygdrive/Z/JDK/jtreg > $ make -C make sanity > /bin/sh: C:/: is a directory > which: no linklint in > (/usr/local/bin:/usr/bin:/cygdrive/c/WINDOWS:/cygdrive/c/WINDOWS/system32:/cyg > drive/c/WINDOWS/System32/Wbem:/cygdrive/c/Program Files/Microsoft > Visual Studio 10.0/Common7/IDE:/cy > gdrive/c/Program Files/Microsoft Visual Studio > 10.0/VC/BIN:/cygdrive/c/Program Files/Microsoft Visua > l Studio > 10.0/Common7/Tools:/cygdrive/c/WINDOWS/Microsoft.NET/Framework/v4.0.30319:/cygdrive/c/Progr > am Files/Microsoft Visual Studio > 10.0/VC/VCPackages:/cygdrive/c/Program Files/Microsoft SDKs/Windows > /v7.0A/bin/NETFX 4.0 Tools:/cygdrive/c/Program Files/Microsoft > SDKs/Windows/v7.0A/bin:/cygdrive/c/Pr > ogram Files/Apache Software > Foundation/apache-ant-1.8.4/bin:/cygdrive/c/Program Files/Apache Softwar > e Foundation/apache-maven-3.0.3/bin) > make: Entering directory `/cygdrive/Z/JDK/jtreg/make' > JDK15HOME = C:/Progra~1/Java/jdk1.6.0_35 > JDK16HOME = C:/Progra~1/Java/jdk1.6.0_35 > JAVAHELP_HOME = Z:/JDK/javahelp/2.0/javahelp > JAVATEST_HOME = Z:/JDK/jtharness > ANTHOME = C:/Progra~1/Apache~2/apache-ant-1.8.4 > XALANHOME = C:/Progra~1/Apache~2/xalan-j_2_7_1 > JUNIT_JAR = Z:/JDK/junit/4.8.2/junit-4.8.2.jar > LINKLINT = > make: Leaving directory `/cygdrive/Z/JDK/jtreg/make' > > From francis.andre.kampbell at orange.fr Thu Oct 17 22:00:56 2013 From: francis.andre.kampbell at orange.fr (Francis ANDRE) Date: Fri, 18 Oct 2013 07:00:56 +0200 Subject: RFR: patch for building jtreg on WXP/W7 In-Reply-To: <5260B8A5.5070600@oracle.com> References: <5260B2AC.8070006@orange.fr> <5260B8A5.5070600@oracle.com> Message-ID: <5260C088.7010306@orange.fr> Jon Le 18/10/2013 06:27, Jonathan Gibbons a ?crit : > Francis, > > I would be interested to see the patches, if you would like to contribute them > back to the main jtreg repo. Sure, I have already a OCA;.. Should I you can forget all patches for the java classes because they are not tested but I did not want to loose their changes, and I do not know how to exclude them in webrev. Should I set a bug in the bug database before publishing the patches or do you want them directly? > > For info on making contributions to OpenJDK, see > http://openjdk.java.net/contribute/ > > -- Jon > > > On 10/17/2013 09:01 PM, Francis ANDRE wrote: >> HI >> >> I made a series of patches for building jtreg on WXP/W7 with cygwin. Patches >> are produced using the webrev.ksh tool. Is somebody interested in getting >> those patches or review them? >> >> Francis >> >> Here my sanity check: >> >> FrancisANDRE at idefix /cygdrive/Z/JDK/jtreg >> $ make -C make sanity >> /bin/sh: C:/: is a directory >> which: no linklint in >> (/usr/local/bin:/usr/bin:/cygdrive/c/WINDOWS:/cygdrive/c/WINDOWS/system32:/cyg >> drive/c/WINDOWS/System32/Wbem:/cygdrive/c/Program Files/Microsoft Visual >> Studio 10.0/Common7/IDE:/cy >> gdrive/c/Program Files/Microsoft Visual Studio >> 10.0/VC/BIN:/cygdrive/c/Program Files/Microsoft Visua >> l Studio >> 10.0/Common7/Tools:/cygdrive/c/WINDOWS/Microsoft.NET/Framework/v4.0.30319:/cygdrive/c/Progr >> am Files/Microsoft Visual Studio 10.0/VC/VCPackages:/cygdrive/c/Program >> Files/Microsoft SDKs/Windows >> /v7.0A/bin/NETFX 4.0 Tools:/cygdrive/c/Program Files/Microsoft >> SDKs/Windows/v7.0A/bin:/cygdrive/c/Pr >> ogram Files/Apache Software >> Foundation/apache-ant-1.8.4/bin:/cygdrive/c/Program Files/Apache Softwar >> e Foundation/apache-maven-3.0.3/bin) >> make: Entering directory `/cygdrive/Z/JDK/jtreg/make' >> JDK15HOME = C:/Progra~1/Java/jdk1.6.0_35 >> JDK16HOME = C:/Progra~1/Java/jdk1.6.0_35 >> JAVAHELP_HOME = Z:/JDK/javahelp/2.0/javahelp >> JAVATEST_HOME = Z:/JDK/jtharness >> ANTHOME = C:/Progra~1/Apache~2/apache-ant-1.8.4 >> XALANHOME = C:/Progra~1/Apache~2/xalan-j_2_7_1 >> JUNIT_JAR = Z:/JDK/junit/4.8.2/junit-4.8.2.jar >> LINKLINT = >> make: Leaving directory `/cygdrive/Z/JDK/jtreg/make' >> >> > > From jonathan.gibbons at oracle.com Fri Oct 18 14:03:51 2013 From: jonathan.gibbons at oracle.com (Jonathan Gibbons) Date: Fri, 18 Oct 2013 14:03:51 -0700 Subject: RFR: patch for building jtreg on WXP/W7 In-Reply-To: <5260C088.7010306@orange.fr> References: <5260B2AC.8070006@orange.fr> <5260B8A5.5070600@oracle.com> <5260C088.7010306@orange.fr> Message-ID: <5261A237.9010308@oracle.com> On 10/17/2013 10:00 PM, Francis ANDRE wrote: > Should I you can forget all patches for the java classes because they > are not tested but I did not want to loose their changes, and I do not > know how to exclude them in webrev. Francis, You can run "hg diff file...." on the files you have modified, containing the changes to contribute. For example, you could go "hg diff make" to create a patch for the changes for files in the make/ directory. I will create the issue in bugs.oracle.com to track this work; once I have the patch, I can post a webrev on cr.openjdk.java.net for you as well. -- Jon From henry.jen at oracle.com Fri Oct 18 16:33:35 2013 From: henry.jen at oracle.com (Henry Jen) Date: Fri, 18 Oct 2013 16:33:35 -0700 Subject: some questions for TestNG support in Jtreg In-Reply-To: <52149ACE.3030701@oracle.com> References: <52149ACE.3030701@oracle.com> Message-ID: <0D977D54-4D10-48E1-AF85-148449DEAA88@oracle.com> Just an idea, not sure if it will work. Did you try to put another copy of Test.properties in a3/b3 with content "TestNG.dirs=."? Cheers, Henry On Aug 21, 2013, at 3:47 AM, patrick zhang wrote: > Hi List, > > I have some functional tests based on TestNG, the dir structure looks like: > ========== > a1/b1/Test1.java > a2/b2/Test2.java > a3/b3/Test3.java > ========== > > For Test1.java and Test2.java, they are located in "a1.b1" or "a2.b2" package really. > But for Test3.java, it is in default package. Here a3/b3 is only simple source directory. > > As you know, we can use TEST.properties to declare source root like below: > ======= > //it can be referenced to Test1 and Test2. Fail to get Test3. > TestNG.dirs = . > ======= > or > ======= > //it can be referenced to Test3. Fail to get Test1 and Test2. > TestNG.dirs = a3/b3 > ======= > > My question is how I can reference to Test1, Test2 and Test3 at same time? It looks "TestNG.dirs = .;a3/b3" or "TestNG.dirs = . a3/b3" does not work. > > FYI, > For some reason I want to keep all structure hierarchy. And I do not want to move Test.java into a3.b3 package. Could it be resolved through TEST.properties directly? > > Regards > Patrick -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.openjdk.java.net/pipermail/jtreg-use/attachments/20131018/0be1c79a/attachment.html From jonathan.gibbons at oracle.com Fri Oct 18 16:46:15 2013 From: jonathan.gibbons at oracle.com (Jonathan Gibbons) Date: Fri, 18 Oct 2013 16:46:15 -0700 Subject: some questions for TestNG support in Jtreg In-Reply-To: <52149ACE.3030701@oracle.com> References: <52149ACE.3030701@oracle.com> Message-ID: <5261C847.7020300@oracle.com> Patrick, Sorry, you can't do what you want. You'll have to move your tests around a bit. If you nominate the directory containing a1 and a2 to be a TestNG directory, then *all* the Java files under that directory will be treated as TestNG tests within the same package hierarchy. You can't mix and match having some files (like those in a1 and a2) exsiting within a package name space and other files (like those in a3/b3) in the unnamed package yet existing within an enclosing package name space. This is no different from having any files existing in a package hierachy -- generally, no other tools would encourage this sort of organization, and jtreg is no exception. I suggest you either move a1, a2 down a level, as in ========== testng/a1/b1/Test1.java testng/a2/b2/Test2.java a3/b3/Test3.java ========== or somewhat equivalently, move a3 up a directory level. -- Jon On 08/21/2013 03:47 AM, patrick zhang wrote: > Hi List, > > I have some functional tests based on TestNG, the dir structure looks > like: > ========== > a1/b1/Test1.java > a2/b2/Test2.java > a3/b3/Test3.java > ========== > > For Test1.java and Test2.java, they are located in "a1.b1" or "a2.b2" > package really. > But for Test3.java, it is in default package. Here a3/b3 is only > simple source directory. > > As you know, we can use TEST.properties to declare source root like below: > ======= > //it can be referenced to Test1 and Test2. Fail to get Test3. > TestNG.dirs = . > ======= > or > ======= > //it can be referenced to Test3. Fail to get Test1 and Test2. > TestNG.dirs = a3/b3 > ======= > > My question is how I can reference to Test1, Test2 and Test3 at same > time? It looks "TestNG.dirs = .;a3/b3" or "TestNG.dirs = . a3/b3" does > not work. > > FYI, > For some reason I want to keep all structure hierarchy. And I do not > want to move Test.java into a3.b3 package. Could it be resolved > through TEST.properties directly? > > Regards > Patrick -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.openjdk.java.net/pipermail/jtreg-use/attachments/20131018/c2e8aa49/attachment.html From francis.andre.kampbell at orange.fr Sun Oct 27 02:53:07 2013 From: francis.andre.kampbell at orange.fr (Francis ANDRE) Date: Sun, 27 Oct 2013 10:53:07 +0100 Subject: Help with jtreg on WXP/Cygwin Message-ID: <526CE283.5050207@orange.fr> Hi jtreg-use list running the jdk7u test bed on a WXP/Cygwin/VS2010 platform, some test fail because jtreg is calling twice kill -9 on the same process id. Where could I fix this issue so that the jdk test run successfully? Francis -------------------------------------------------- TEST: com/sun/jdi/ArrayLengthDumpTest.sh JDK under test: (Z:\JDK\jdk7u\build\WINDOW~1\J2SDK-~1) openjdk version "1.7.0-internal" OpenJDK Runtime Environment (build 1.7.0-internal-francisandre_2013_10_18_20_47-b00) OpenJDK Client VM (build 24.60-b01, interpreted mode) ACTION: shell -- Failed. Execution failed: exit code 1 REASON: User specified action: run shell ArrayLengthDumpTest.sh TIME: 10.313 seconds messages: command: shell ArrayLengthDumpTest.sh reason: User specified action: run shell ArrayLengthDumpTest.sh elapsed time (seconds): 10.313 STDOUT: --Compiling first version of /cygdrive/z/JDK/jdk7u/build/windows-i586/testoutput/jdk_jdi/JTwork/classes/com/sun/jdi/aa3544/ArrayLengthDumpTarg.java with options: compiling ArrayLengthDumpTarg.java --Starting jdb, address=kkkk.3544 --Starting debuggee Listening at address: kkkk.3544 STDERR: ShellScaffold.sh: Version -- jdb process info ---------------------- 11932 TTY -Dapplication.home=Z:\JDK\jdk7u\build\WINDOW~1\J2SDK-~1 -Xms8m -DHANGINGJAVA-3544_JDB -- jdb threads: jstack 11932 2013-10-27 09:31:14 Full thread dump OpenJDK Client VM (24.60-b01 mixed mode): "Service Thread" daemon prio=6 tid=0x02e32c00 nid=0x2d3c runnable [0x00000000] java.lang.Thread.State: RUNNABLE "C1 CompilerThread0" daemon prio=10 tid=0x02e24c00 nid=0x1d60 waiting on condition [0x00000000] java.lang.Thread.State: RUNNABLE "Attach Listener" daemon prio=10 tid=0x02e23400 nid=0x2c4c waiting on condition [0x00000000] java.lang.Thread.State: RUNNABLE "Signal Dispatcher" daemon prio=10 tid=0x02e22400 nid=0x600 runnable [0x00000000] java.lang.Thread.State: RUNNABLE "Finalizer" daemon prio=8 tid=0x02be0800 nid=0xa18 in Object.wait() [0x02e1f000] java.lang.Thread.State: WAITING (on object monitor) at java.lang.Object.wait(Native Method) - waiting on <0x100353f8> (a java.lang.ref.ReferenceQueue$Lock) at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:135) - locked <0x100353f8> (a java.lang.ref.ReferenceQueue$Lock) at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:151) at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:189) "Reference Handler" daemon prio=10 tid=0x02bdb800 nid=0x2ef4 in Object.wait() [0x02dcf000] java.lang.Thread.State: WAITING (on object monitor) at java.lang.Object.wait(Native Method) - waiting on <0x10034fd0> (a java.lang.ref.Reference$Lock) at java.lang.Object.wait(Object.java:503) at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:133) - locked <0x10034fd0> (a java.lang.ref.Reference$Lock) "main" prio=6 tid=0x003c9800 nid=0x19dc runnable [0x009ef000] java.lang.Thread.State: RUNNABLE at com.sun.tools.jdi.SharedMemoryTransportService.accept0(Native Method) at com.sun.tools.jdi.SharedMemoryTransportService.accept(SharedMemoryTransportService.java:164) at com.sun.tools.jdi.GenericListeningConnector.accept(GenericListeningConnector.java:151) at com.sun.tools.example.debug.tty.VMConnection.listenTarget(VMConnection.java:536) at com.sun.tools.example.debug.tty.VMConnection.open(VMConnection.java:330) - locked <0x101f28a0> (a com.sun.tools.example.debug.tty.VMConnection) at com.sun.tools.example.debug.tty.Env.init(Env.java:63) at com.sun.tools.example.debug.tty.TTY.main(TTY.java:1066) "VM Thread" prio=10 tid=0x02bd9c00 nid=0x2260 runnable "VM Periodic Task Thread" prio=10 tid=0x02e34c00 nid=0x1694 waiting on condition JNI global references: 121 ------------------------------------------ cleanup: kill -9 4804*** **cleanup: kill -9 4804 * Z:/JDK/jdk7u/jdk/test/com/sun/jdi/ShellScaffold.sh: line 191: kill: (4804) - No such process rerun: 'PATH=C:/cygwin/usr/local/bin;C:/cygwin/bin;C:/WINDOWS;C:/WINDOWS/system32;C:/WINDOWS/System32/Wbem;C:/Program Files/Microsoft Visual Studio 10.0/Common7/IDE;C:/Program Files/Microsoft Visual Studio 10.0/VC/BIN;C:/Program Files/Microsoft Visual Studio 10.0/Common7/Tools;C:/WINDOWS/Microsoft.NET/Framework/v4.0.30319;C:/Program Files/Microsoft Visual Studio 10.0/VC/VCPackages;C:/Program Files/Microsoft SDKs/Windows/v7.0A/bin/NETFX 4.0 Tools;C:/Program Files/Microsoft SDKs/Windows/v7.0A/bin;C:/Program Files/Apache Software Foundation/apache-ant-1.8.4/bin;C:/Program Files/Apache Software Foundation/apache-maven-3.0.3/bin' \ SystemDrive=C: \ SystemRoot=C:/WINDOWS \ TEMP=C:/cygwin/tmp \ TMP=C:/DOCUME~1/FRANCI~1/LOCALS~1/Temp \ windir=C:/WINDOWS \ TESTSRC=Z:/JDK/jdk7u/jdk/test/com/sun/jdi \ TESTSRCPATH=Z:/JDK/jdk7u/jdk/test/com/sun/jdi \ TESTCLASSES=Z:/JDK/jdk7u/build/windows-i586/testoutput/jdk_jdi/JTwork/classes/com/sun/jdi \ TESTCLASSPATH=Z:/JDK/jdk7u/build/windows-i586/testoutput/jdk_jdi/JTwork/classes/com/sun/jdi \ COMPILEJAVA=Z:/JDK/jdk7u/build/WINDOW~1/J2SDK-~1 \ TESTJAVA=Z:/JDK/jdk7u/build/WINDOW~1/J2SDK-~1 \ 'TESTVMOPTS=-ea -esa -Xint' \ 'TESTTOOLVMOPTS=-J-ea -J-esa -J-Xint' \ TESTJAVACOPTS= \ TESTJAVAOPTS= \ TESTTIMEOUTFACTOR=4.0 \ sh \ 'Z:\JDK\jdk7u\jdk\test\com\sun\jdi\ArrayLengthDumpTest.sh' TEST RESULT: Failed. Execution failed: exit code 1 -------------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.openjdk.java.net/pipermail/jtreg-use/attachments/20131027/dd3a7a41/attachment.html From jonathan.gibbons at oracle.com Mon Oct 28 11:56:12 2013 From: jonathan.gibbons at oracle.com (Jonathan Gibbons) Date: Mon, 28 Oct 2013 11:56:12 -0700 Subject: Help with jtreg on WXP/Cygwin In-Reply-To: <526CE283.5050207@orange.fr> References: <526CE283.5050207@orange.fr> Message-ID: <526EB34C.9090104@oracle.com> This looks more like an issue with a specific test than with the jtreg tool itself. I suggest posting your question on core-libs-dev. -- Jon On 10/27/2013 02:53 AM, Francis ANDRE wrote: > Hi jtreg-use list > > running the jdk7u test bed on a WXP/Cygwin/VS2010 platform, some test > fail because jtreg is calling twice kill -9 on the same process id. > Where could I fix this issue so that the jdk test run successfully? > > Francis > > -------------------------------------------------- > TEST: com/sun/jdi/ArrayLengthDumpTest.sh > JDK under test: (Z:\JDK\jdk7u\build\WINDOW~1\J2SDK-~1) > openjdk version "1.7.0-internal" > OpenJDK Runtime Environment (build > 1.7.0-internal-francisandre_2013_10_18_20_47-b00) > OpenJDK Client VM (build 24.60-b01, interpreted mode) > > > > ACTION: shell -- Failed. Execution failed: exit code 1 > REASON: User specified action: run shell ArrayLengthDumpTest.sh > TIME: 10.313 seconds > messages: > command: shell ArrayLengthDumpTest.sh > reason: User specified action: run shell ArrayLengthDumpTest.sh > elapsed time (seconds): 10.313 > STDOUT: > --Compiling first version of > /cygdrive/z/JDK/jdk7u/build/windows-i586/testoutput/jdk_jdi/JTwork/classes/com/sun/jdi/aa3544/ArrayLengthDumpTarg.java > with options: > compiling ArrayLengthDumpTarg.java > > --Starting jdb, address=kkkk.3544 > --Starting debuggee > Listening at address: kkkk.3544 > STDERR: > ShellScaffold.sh: Version > -- jdb process info ---------------------- > 11932 TTY > -Dapplication.home=Z:\JDK\jdk7u\build\WINDOW~1\J2SDK-~1 -Xms8m > -DHANGINGJAVA-3544_JDB > -- jdb threads: jstack 11932 > 2013-10-27 09:31:14 > Full thread dump OpenJDK Client VM (24.60-b01 mixed mode): > > "Service Thread" daemon prio=6 tid=0x02e32c00 nid=0x2d3c runnable > [0x00000000] > java.lang.Thread.State: RUNNABLE > > "C1 CompilerThread0" daemon prio=10 tid=0x02e24c00 nid=0x1d60 waiting > on condition [0x00000000] > java.lang.Thread.State: RUNNABLE > > "Attach Listener" daemon prio=10 tid=0x02e23400 nid=0x2c4c waiting on > condition [0x00000000] > java.lang.Thread.State: RUNNABLE > > "Signal Dispatcher" daemon prio=10 tid=0x02e22400 nid=0x600 runnable > [0x00000000] > java.lang.Thread.State: RUNNABLE > > "Finalizer" daemon prio=8 tid=0x02be0800 nid=0xa18 in Object.wait() > [0x02e1f000] > java.lang.Thread.State: WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > - waiting on <0x100353f8> (a java.lang.ref.ReferenceQueue$Lock) > at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:135) > - locked <0x100353f8> (a java.lang.ref.ReferenceQueue$Lock) > at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:151) > at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:189) > > "Reference Handler" daemon prio=10 tid=0x02bdb800 nid=0x2ef4 in > Object.wait() [0x02dcf000] > java.lang.Thread.State: WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > - waiting on <0x10034fd0> (a java.lang.ref.Reference$Lock) > at java.lang.Object.wait(Object.java:503) > at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:133) > - locked <0x10034fd0> (a java.lang.ref.Reference$Lock) > > "main" prio=6 tid=0x003c9800 nid=0x19dc runnable [0x009ef000] > java.lang.Thread.State: RUNNABLE > at com.sun.tools.jdi.SharedMemoryTransportService.accept0(Native > Method) > at > com.sun.tools.jdi.SharedMemoryTransportService.accept(SharedMemoryTransportService.java:164) > at > com.sun.tools.jdi.GenericListeningConnector.accept(GenericListeningConnector.java:151) > at > com.sun.tools.example.debug.tty.VMConnection.listenTarget(VMConnection.java:536) > at > com.sun.tools.example.debug.tty.VMConnection.open(VMConnection.java:330) > - locked <0x101f28a0> (a com.sun.tools.example.debug.tty.VMConnection) > at com.sun.tools.example.debug.tty.Env.init(Env.java:63) > at com.sun.tools.example.debug.tty.TTY.main(TTY.java:1066) > > "VM Thread" prio=10 tid=0x02bd9c00 nid=0x2260 runnable > > "VM Periodic Task Thread" prio=10 tid=0x02e34c00 nid=0x1694 waiting on > condition > > JNI global references: 121 > > ------------------------------------------ > > cleanup: kill -9 4804*** > **cleanup: kill -9 4804 * > Z:/JDK/jdk7u/jdk/test/com/sun/jdi/ShellScaffold.sh: line 191: kill: > (4804) - No such process > rerun: > 'PATH=C:/cygwin/usr/local/bin;C:/cygwin/bin;C:/WINDOWS;C:/WINDOWS/system32;C:/WINDOWS/System32/Wbem;C:/Program > Files/Microsoft Visual Studio 10.0/Common7/IDE;C:/Program > Files/Microsoft Visual Studio 10.0/VC/BIN;C:/Program Files/Microsoft > Visual Studio > 10.0/Common7/Tools;C:/WINDOWS/Microsoft.NET/Framework/v4.0.30319;C:/Program > Files/Microsoft Visual Studio 10.0/VC/VCPackages;C:/Program > Files/Microsoft SDKs/Windows/v7.0A/bin/NETFX 4.0 Tools;C:/Program > Files/Microsoft SDKs/Windows/v7.0A/bin;C:/Program Files/Apache > Software Foundation/apache-ant-1.8.4/bin;C:/Program Files/Apache > Software Foundation/apache-maven-3.0.3/bin' \ > SystemDrive=C: \ > SystemRoot=C:/WINDOWS \ > TEMP=C:/cygwin/tmp \ > TMP=C:/DOCUME~1/FRANCI~1/LOCALS~1/Temp \ > windir=C:/WINDOWS \ > TESTSRC=Z:/JDK/jdk7u/jdk/test/com/sun/jdi \ > TESTSRCPATH=Z:/JDK/jdk7u/jdk/test/com/sun/jdi \ > TESTCLASSES=Z:/JDK/jdk7u/build/windows-i586/testoutput/jdk_jdi/JTwork/classes/com/sun/jdi > \ > TESTCLASSPATH=Z:/JDK/jdk7u/build/windows-i586/testoutput/jdk_jdi/JTwork/classes/com/sun/jdi > \ > COMPILEJAVA=Z:/JDK/jdk7u/build/WINDOW~1/J2SDK-~1 \ > TESTJAVA=Z:/JDK/jdk7u/build/WINDOW~1/J2SDK-~1 \ > 'TESTVMOPTS=-ea -esa -Xint' \ > 'TESTTOOLVMOPTS=-J-ea -J-esa -J-Xint' \ > TESTJAVACOPTS= \ > TESTJAVAOPTS= \ > TESTTIMEOUTFACTOR=4.0 \ > sh \ > 'Z:\JDK\jdk7u\jdk\test\com\sun\jdi\ArrayLengthDumpTest.sh' > > TEST RESULT: Failed. Execution failed: exit code 1 > -------------------------------------------------- > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.openjdk.java.net/pipermail/jtreg-use/attachments/20131028/f8ce16e8/attachment.html From Alan.Bateman at oracle.com Mon Oct 28 12:29:37 2013 From: Alan.Bateman at oracle.com (Alan Bateman) Date: Mon, 28 Oct 2013 19:29:37 +0000 Subject: Help with jtreg on WXP/Cygwin In-Reply-To: <526EB34C.9090104@oracle.com> References: <526CE283.5050207@orange.fr> <526EB34C.9090104@oracle.com> Message-ID: <526EBB21.2030503@oracle.com> On 28/10/2013 18:56, Jonathan Gibbons wrote: > This looks more like an issue with a specific test than with the jtreg > tool itself. I suggest posting your question on core-libs-dev. > > -- Jon JDI = "Java Debug Interface" so serviceability-dev would be the right mailing list (it might not be this one test, many of the JDI tests make use of the same test framework). -Alan -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.openjdk.java.net/pipermail/jtreg-use/attachments/20131028/9671cf77/attachment.html From jonathan.gibbons at oracle.com Tue Oct 29 14:42:15 2013 From: jonathan.gibbons at oracle.com (Jonathan Gibbons) Date: Tue, 29 Oct 2013 14:42:15 -0700 Subject: RFR: patch for building jtreg on WXP/W7 In-Reply-To: <5261A237.9010308@oracle.com> References: <5260B2AC.8070006@orange.fr> <5260B8A5.5070600@oracle.com> <5260C088.7010306@orange.fr> <5261A237.9010308@oracle.com> Message-ID: <52702BB7.4010300@oracle.com> On 10/18/2013 02:03 PM, Jonathan Gibbons wrote: > On 10/17/2013 10:00 PM, Francis ANDRE wrote: >> Should I you can forget all patches for the java classes because they >> are not tested but I did not want to loose their changes, and I do >> not know how to exclude them in webrev. > > Francis, > > You can run "hg diff file...." on the files you have modified, > containing the changes to contribute. For example, you could go "hg > diff make" to create a patch for the changes for files in the make/ > directory. > > I will create the issue in bugs.oracle.com to track this work; once I > have the patch, I can post a webrev on cr.openjdk.java.net for you as > well. > > -- Jon Francis, Thank you for your contribution, which has now been commited and pushed as this changeset: http://hg.openjdk.java.net/code-tools/jtreg/rev/9d283fa28b97 The issue for this work is/was: https://bugs.openjdk.java.net/browse/CODETOOLS-7900245 -- Jon From jonathan.gibbons at oracle.com Wed Oct 30 18:41:55 2013 From: jonathan.gibbons at oracle.com (Jonathan Gibbons) Date: Wed, 30 Oct 2013 18:41:55 -0700 Subject: building jtreg, and running tests Message-ID: <5271B563.7010301@oracle.com> Spurred on by the recent discussions and contributions, I've pushed some more changes to the jtreg repo to make it easier to build, and even run most of the tests, on Windows. (I still recommend using Linux instead, when that is an option.) The cygwin world is definitely problematic, especially for running the jtreg tests, since cygwin presents a different view of the file system to the native Windows view seen by Java programs. The problems mostly show up in tests that check that output from jtreg, especially when using diff, grep, etc. For the time being, I've disabled the tests in 11 of the 70 test files in make/tests/*.gmk, meaning that the tests in the remaining 59 files all run successfully. For what its worth, my setup is to have a cygwin symlink from /opt to C:/opt (i.e. /cygdrive/c/opt) which means that I can place all my dependencies in /opt//package///version/ and can then see them from both the cygwin world and the Windows world, without having to use path-munging utilities like cygpath all over the place. I'm open to more direct support of /cygdrive paths in the build, and wonder if folk have any good tips and tricks for minimising the obtrusiveness of the conversion functions in the composite world of GNU make and cygwin, such that the resulting code runs on Cygwin and POSIX systems. -- Jon -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.openjdk.java.net/pipermail/jtreg-use/attachments/20131030/37c9b900/attachment.html From francis.andre.kampbell at orange.fr Thu Oct 31 13:27:36 2013 From: francis.andre.kampbell at orange.fr (Francis ANDRE) Date: Thu, 31 Oct 2013 21:27:36 +0100 Subject: building jtreg, and running tests In-Reply-To: <5271B563.7010301@oracle.com> References: <5271B563.7010301@oracle.com> Message-ID: <5272BD38.6090409@orange.fr> Hi Jon I run all the jdk8 test on WXP/Cygwin with your latest version of jtreg and found this problem: $ JT_JAVA=/cygdrive/Z/JDK/jdk8/build/windows-x86-normal-server-release/images/j2sdk-image Z:/JDK/jt reg/build/images/jtreg/win32/bin/jtreg -J-Xmx512m -vmoption:-Xmx768m -a -ignore:quiet -v:fail,e rror,nopass -r:Z:/JDK/jdk8/LANGTO~1/build/WINDOW~1/test/LANGTO~1/jtreg/JTreport -w:Z:/JDK/jdk8/LANGTO~1/build/WINDOW~1/test/LANGTO~1/jtreg/JTwork -jdk:/cygdrive/Z/JDK/j dk8/build/windows-x86-normal-server-release/images/j2sdk-image -agentvm -concurrency:2 . || ( status=$?; if [ $status -ge 3 ]; then exit $status ; fi ; echo $status > Z:/ JDK/jdk8/LANGTO~1/build/WINDOW~1/test/LANGTO~1/jtreg/status.txt ) Error: JDK not found: \cygdrive\Z\JDK\jdk8\build\windows-x86-normal-server-release\images\j2sdk-imag e The error JDK not found is coming from the replacement of the / by \ in the JT_JAVA environment variable. In effect, the cygwin path should be with "/" and not "\"... -- I know, it is a nightmare --...hopefully,we will beat it! Francis Le 31/10/2013 02:41, Jonathan Gibbons a ?crit : > Spurred on by the recent discussions and contributions, I've pushed some more > changes to the jtreg repo to make it easier to build, and even run most of the > tests, on Windows. > > (I still recommend using Linux instead, when that is an option.) > > The cygwin world is definitely problematic, especially for running the jtreg > tests, since cygwin presents a different view of the file system to the native > Windows view seen by Java programs. The problems mostly show up in tests that > check that output from jtreg, especially when using diff, grep, etc. For the > time being, I've disabled the tests in 11 of the 70 test files in > make/tests/*.gmk, meaning that the tests in the remaining 59 files all run > successfully. > > For what its worth, my setup is to have a cygwin symlink from /opt to C:/opt > (i.e. /cygdrive/c/opt) which means that I can place all my dependencies in > /opt//package///version/ and can then see them from both the cygwin world and > the Windows world, without having to use path-munging utilities like cygpath > all over the place. > > I'm open to more direct support of /cygdrive paths in the build, and wonder if > folk have any good tips and tricks for minimising the obtrusiveness of the > conversion functions in the composite world of GNU make and cygwin, such that > the resulting code runs on Cygwin and POSIX systems. > > -- Jon > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.openjdk.java.net/pipermail/jtreg-use/attachments/20131031/2f4b7f26/attachment.html From jonathan.gibbons at oracle.com Thu Oct 31 13:39:46 2013 From: jonathan.gibbons at oracle.com (Jonathan Gibbons) Date: Thu, 31 Oct 2013 13:39:46 -0700 Subject: building jtreg, and running tests In-Reply-To: <5272BD38.6090409@orange.fr> References: <5271B563.7010301@oracle.com> <5272BD38.6090409@orange.fr> Message-ID: <5272C012.7070300@oracle.com> Currently, neither the jtreg build, nor the jtreg execution script is cygwin-aware, meaning there is not explicit support for using /cygdrive/* paths. I am working to fix that. -- Jon On 10/31/2013 01:27 PM, Francis ANDRE wrote: > Hi Jon > > I run all the jdk8 test on WXP/Cygwin with your latest version of > jtreg and found this problem: > > $ > JT_JAVA=/cygdrive/Z/JDK/jdk8/build/windows-x86-normal-server-release/images/j2sdk-image > Z:/JDK/jt > reg/build/images/jtreg/win32/bin/jtreg -J-Xmx512m -vmoption:-Xmx768m > -a -ignore:quiet -v:fail,e > rror,nopass > -r:Z:/JDK/jdk8/LANGTO~1/build/WINDOW~1/test/LANGTO~1/jtreg/JTreport > -w:Z:/JDK/jdk8/LANGTO~1/build/WINDOW~1/test/LANGTO~1/jtreg/JTwork > -jdk:/cygdrive/Z/JDK/j > dk8/build/windows-x86-normal-server-release/images/j2sdk-image > -agentvm -concurrency:2 > . || ( status=$?; if [ $status -ge 3 ]; then exit $status > ; fi ; echo $status > Z:/ > JDK/jdk8/LANGTO~1/build/WINDOW~1/test/LANGTO~1/jtreg/status.txt ) > Error: JDK not found: > \cygdrive\Z\JDK\jdk8\build\windows-x86-normal-server-release\images\j2sdk-imag > e > > The error JDK not found is coming from the replacement of the / by \ > in the JT_JAVA environment variable. In effect, the cygwin path should > be with "/" and not "\"... -- I know, it is a nightmare > --...hopefully,we will beat it! > > Francis > > Le 31/10/2013 02:41, Jonathan Gibbons a ?crit : >> Spurred on by the recent discussions and contributions, I've pushed >> some more changes to the jtreg repo to make it easier to build, and >> even run most of the tests, on Windows. >> >> (I still recommend using Linux instead, when that is an option.) >> >> The cygwin world is definitely problematic, especially for running >> the jtreg tests, since cygwin presents a different view of the file >> system to the native Windows view seen by Java programs. The problems >> mostly show up in tests that check that output from jtreg, especially >> when using diff, grep, etc. For the time being, I've disabled the >> tests in 11 of the 70 test files in make/tests/*.gmk, meaning that >> the tests in the remaining 59 files all run successfully. >> >> For what its worth, my setup is to have a cygwin symlink from /opt to >> C:/opt (i.e. /cygdrive/c/opt) which means that I can place all my >> dependencies in /opt//package///version/ and can then see them from >> both the cygwin world and the Windows world, without having to use >> path-munging utilities like cygpath all over the place. >> >> I'm open to more direct support of /cygdrive paths in the build, and >> wonder if folk have any good tips and tricks for minimising the >> obtrusiveness of the conversion functions in the composite world of >> GNU make and cygwin, such that the resulting code runs on Cygwin and >> POSIX systems. >> >> -- Jon >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.openjdk.java.net/pipermail/jtreg-use/attachments/20131031/8972143c/attachment.html From jonathan.gibbons at oracle.com Thu Oct 31 16:51:25 2013 From: jonathan.gibbons at oracle.com (Jonathan Gibbons) Date: Thu, 31 Oct 2013 16:51:25 -0700 Subject: Jtreg setup under Windows 7/8 In-Reply-To: <51B7A1A1.4090905@reini.net> References: <51B78B2E.3020208@reini.net> <51B798CF.7020004@reini.net> <51B79F4F.5000100@oracle.com> <51B7A1A1.4090905@reini.net> Message-ID: <5272ECFD.1030904@oracle.com> I finally got a chance to get to the bottom of the problems you were having. There is a bug in the script that you triggered with the settings you were using: export JAVA_HOME=/cygdrive/c/Java/jdk1.7.0_21 export JT_HOME=/cygdrive/c/OpenJDK/jtreg export PRODUCT_HOME=/cygdrive/c/OpenJDK/jdk8_tl/build/windows-x86_64-normal-server-release/images/j2sdk-image export PATH=${JAVA_HOME}/bin:${JT_HOME}/win32/bin:${PATH} The trigger was the second line, setting JT_HOME. Normally, you do not need to set that, and the script will infer the value based on the location of the script. In that case, it will use "cygpath" to normalize the file path. But the normalization does not happen if you explicitly set the value of JT_HOME, and therein lies the bug. -- Jon On 06/11/2013 03:16 PM, Patrick Reinhart wrote: > Hi Jon, > > After some research with Martijn Verburg we found out the if the class > path to the jtreg.jar is specified in a absolute way, it won't work. > Using a relative path does the thing... > > Cheers > > openjdk at openjdk-win-7 /cygdrive/c/OpenJDK/jtreg/lib > $ /cygdrive/c/Java/jdk1.7.0_21/bin/java -classpath > /cygdrive/c/OpenJDK/jtreg/lib/jtreg.jar > com.sun.javatest.regtest.GetSystemProperty java.version > Error: Could not find or load main class > com.sun.javatest.regtest.GetSystemProperty > > openjdk at openjdk-win-7 /cygdrive/c/OpenJDK/jtreg > $ /cygdrive/c/Java/jdk1.7.0_21/bin/java -classpath lib/jtreg.jar > com.sun.javatest.regtest.GetSystemProperty java.version > java.version=1.7.0_21 > > openjdk at openjdk-win-7 /cygdrive/c/OpenJDK/jtreg/lib > $ /cygdrive/c/Java/jdk1.7.0_21/bin/java -classpath jtreg.jar > com.sun.javatest.regtest.GetSystemProperty > java.version java.version=1.7.0_21 > > > > > On 06/12/2013 12:06 AM, Jonathan Gibbons wrote: >> The jtreg script is having trouble identifying which version of Java >> to use. It should be detecting your setting of JAVA_HOME, but is >> failing for some readon. You could try setting JT_JAVA to either >> >> export JT_JAVA=/cygdrive/c/Java/jdk1.7.0_21 >> >> or >> >> export JT_JAVA=/cygdrive/c/Java/jdk1.7.0_21/bin/java >> >> >> -- Jon >> >> >> >> On 06/11/2013 02:38 PM, Patrick Reinhart wrote: >>> Hi Mike, >>> >>> I just began to set it up after I have built jdk8_tl that extracted >>> the binary and set up the following cygwin exports: >>> >>> export JAVA_HOME=/cygdrive/c/Java/jdk1.7.0_21 >>> export JT_HOME=/cygdrive/c/OpenJDK/jtreg >>> export >>> PRODUCT_HOME=/cygdrive/c/OpenJDK/jdk8_tl/build/windows-x86_64-normal-server-release/images/j2sdk-image >>> export PATH=${JAVA_HOME}/bin:${JT_HOME}/win32/bin:${PATH} >>> >>> After that I did some basic tests: >>> >>> $ java -version >>> java version "1.7.0_21" >>> Java(TM) SE Runtime Environment (build 1.7.0_21-b11) >>> Java HotSpot(TM) 64-Bit Server VM (build 23.21-b01, mixed mode) >>> >>> $ jtreg >>> Cannot determine version of java to run jtreg >>> >>> What could cause this problem? >>> >>> Cheers >>> >>> Patrick >>> >>> On 06/11/2013 10:59 PM, Mike Duigou wrote: >>>> What's failing? which OpenJDK repo are you trying to run it >>>> against? Which tests are you trying to run? etc. >>>> >>>> Mike >>>> >>>> On Jun 11 2013, at 13:40 , Patrick Reinhart wrote: >>>> >>>>> Hi everybody, >>>>> >>>>> I just set up a new build environment under Windows 8 and try to >>>>> also set up Jtreg after a successful build. But until now with not >>>>> lot much luck. >>>>> >>>>> I use the binary version jtreg-4.1-bin-b05_29_nov_2012.zip from >>>>> http://download.java.net/openjdk/jtreg. >>>>> >>>>> >>>>> Does anyone have a hint what kind of variables have to be set >>>>> under Cygwin? >>>>> >>>>> Cheers Patrick >>> >> > From jonathan.gibbons at oracle.com Thu Oct 31 19:40:39 2013 From: jonathan.gibbons at oracle.com (Jonathan Gibbons) Date: Thu, 31 Oct 2013 19:40:39 -0700 Subject: building jtreg, and running tests In-Reply-To: <5272BD38.6090409@orange.fr> References: <5271B563.7010301@oracle.com> <5272BD38.6090409@orange.fr> Message-ID: <527314A7.3040500@oracle.com> Francis, The problem is not the type of file separator (\ vs. /) but the use of /cygdrive paths. Java, like most other programs that run natively on Windows, does not recognize cygwin file paths, which are only valid within the general cygwin environment. This extends to jtreg (or more specifically, the classes in jtreg.jar). Separately, even though \ is the standard file separator on Windows, it has long been specified that / is also a valid separator on Windows. Put these two statements together, and it follows that when you pass a path like /cygdrive/Z/my/directory/file.txt to a Java program, the program will typically interpret that as X:\cygdrive\Z\my\directory\file.txt, where X is the drive letter for the current working directory. Typically, that path will not exist and you will get some sort of "file not found error" if you try and access that file. And that is what you are seeing below. There are two solutions, each with their own advantages and disadvantages: 1. Use "mixed style" paths, like Z:/my/directory/file.txt. Windows (and java programs) will accept them as valid paths, but the ":" character can cause problems in the cygwin world 2. Use the standard cygpath utility to convert between the different formats as needed. See http://cygwin.com/cygwin-ug-net/using-effectively.html for more information. In particular, see this section: > > > Pathnames > > Windows programs do not understand POSIX pathnames, so any arguments > that reference the filesystem must be in Windows (or DOS) format or > translated. Cygwin provides the *cygpath* utility for converting > between Windows and POSIX paths. A complete description of its options > and examples of its usage are in the section called "cygpath" > , including > a shell script for starting Windows Explorer in any directory. The > same format works for most Windows programs, for example > > |notepad.exe "$(cygpath -aw "Desktop/Phone Numbers.txt")"| > > A few programs require a Windows-style, semicolon-delimited path list, > which *cygpath* can translate from a POSIX path with the |-p| option. > For example, a Java compilation from *bash* might look like this: > > |javac -cp "$(cygpath -pw "$CLASSPATH")" hello.java| > > Since using quoting and subshells is somewhat awkward, it is often > preferable to use *cygpath* in shell scripts. > So, where does that leave jtreg? Well, internally the code is just a Java program, and so does not (will not) understand /cygdrive paths. But, it is reasonable to expect that those parts of the jtreg ecosystem that live in the cygwin world should be aware of /cygdrive paths. Earlier today, I pushed fixes that should allow /cygdrive paths to be used when building jtreg. http://hg.openjdk.java.net/code-tools/jtreg/rev/8f44b4e1f37b and tolerate the use of /cygdrive in JT_HOME http://hg.openjdk.java.net/code-tools/jtreg/rev/caf396306070 Your example has opened up another case that would be good to address, command line args to jtreg. For those folk that invoke jtreg through the standard script, we could reasonably translate /cygdrive/X into X: for all drive letters. Those folk that invoke jtreg.jar file directly will need to do the translation themselves. Note: Some folk may use jtreg by means of the various test targets in the various Makefiles. I don't know what the conventions are for accepting /cygdrive paths in the makefiles, or whether the mixed format is expected/required. Maybe someone more familiar with using those makefiles on Windows with Cygwin can comment. For another day: What about MSYS/MinGW? If you want your head to explode, try reading http://www.mingw.org/wiki/Posix_path_conversion -- Jon On 10/31/2013 01:27 PM, Francis ANDRE wrote: > Hi Jon > > I run all the jdk8 test on WXP/Cygwin with your latest version of > jtreg and found this problem: > > $ > JT_JAVA=/cygdrive/Z/JDK/jdk8/build/windows-x86-normal-server-release/images/j2sdk-image > Z:/JDK/jt > reg/build/images/jtreg/win32/bin/jtreg -J-Xmx512m -vmoption:-Xmx768m > -a -ignore:quiet -v:fail,e > rror,nopass > -r:Z:/JDK/jdk8/LANGTO~1/build/WINDOW~1/test/LANGTO~1/jtreg/JTreport > -w:Z:/JDK/jdk8/LANGTO~1/build/WINDOW~1/test/LANGTO~1/jtreg/JTwork > -jdk:/cygdrive/Z/JDK/j > dk8/build/windows-x86-normal-server-release/images/j2sdk-image > -agentvm -concurrency:2 > . || ( status=$?; if [ $status -ge 3 ]; then exit $status > ; fi ; echo $status > Z:/ > JDK/jdk8/LANGTO~1/build/WINDOW~1/test/LANGTO~1/jtreg/status.txt ) > Error: JDK not found: > \cygdrive\Z\JDK\jdk8\build\windows-x86-normal-server-release\images\j2sdk-imag > e > > The error JDK not found is coming from the replacement of the / by \ > in the JT_JAVA environment variable. In effect, the cygwin path should > be with "/" and not "\"... -- I know, it is a nightmare > --...hopefully,we will beat it! > > Francis > > Le 31/10/2013 02:41, Jonathan Gibbons a ?crit : >> Spurred on by the recent discussions and contributions, I've pushed >> some more changes to the jtreg repo to make it easier to build, and >> even run most of the tests, on Windows. >> >> (I still recommend using Linux instead, when that is an option.) >> >> The cygwin world is definitely problematic, especially for running >> the jtreg tests, since cygwin presents a different view of the file >> system to the native Windows view seen by Java programs. The problems >> mostly show up in tests that check that output from jtreg, especially >> when using diff, grep, etc. For the time being, I've disabled the >> tests in 11 of the 70 test files in make/tests/*.gmk, meaning that >> the tests in the remaining 59 files all run successfully. >> >> For what its worth, my setup is to have a cygwin symlink from /opt to >> C:/opt (i.e. /cygdrive/c/opt) which means that I can place all my >> dependencies in /opt//package///version/ and can then see them from >> both the cygwin world and the Windows world, without having to use >> path-munging utilities like cygpath all over the place. >> >> I'm open to more direct support of /cygdrive paths in the build, and >> wonder if folk have any good tips and tricks for minimising the >> obtrusiveness of the conversion functions in the composite world of >> GNU make and cygwin, such that the resulting code runs on Cygwin and >> POSIX systems. >> >> -- Jon >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.openjdk.java.net/pipermail/jtreg-use/attachments/20131031/f9265c23/attachment-0001.html From mike.duigou at oracle.com Thu Oct 31 20:16:07 2013 From: mike.duigou at oracle.com (Mike Duigou) Date: Thu, 31 Oct 2013 20:16:07 -0700 Subject: building jtreg, and running tests In-Reply-To: <527314A7.3040500@oracle.com> References: <5271B563.7010301@oracle.com> <5272BD38.6090409@orange.fr> <527314A7.3040500@oracle.com> Message-ID: On Oct 31 2013, at 19:40 , Jonathan Gibbons wrote: > > Earlier today, I pushed fixes that should allow /cygdrive paths to be used when building jtreg. > http://hg.openjdk.java.net/code-tools/jtreg/rev/8f44b4e1f37b > and tolerate the use of /cygdrive in JT_HOME > http://hg.openjdk.java.net/code-tools/jtreg/rev/caf396306070 > > Your example has opened up another case that would be good to address, command line args to jtreg. For those folk that invoke jtreg through the standard script, we could reasonably translate /cygdrive/X into X: for all drive letters. I believe we will have to move towards this. > Those folk that invoke jtreg.jar file directly will need to do the translation themselves. I agree. The java -jar command should only be seeing native paths. > Some folk may use jtreg by means of the various test targets in the various Makefiles. I don't know what the conventions are for accepting /cygdrive paths in the makefiles, or whether the mixed format is expected/required. Maybe someone more familiar with using those makefiles on Windows with Cygwin can comment. I have been working on the test/Makefiles and have been thinking where to properly make the split between native paths and cygwin paths. Currently it's done all in the makefile but perhaps in the jtreg script wrapper might be a better place (or more convenient) since it is going to get invoked anyway and will always be invoked from within a posix-like environment like either cygwin or mingw. This would also eliminate the need to have platform specific code in the test makefiles which would be nice. Another option I have considered: Windows command scripts to replace or supplement the jtreg and jtdiff scripts that would be fully windows native. I'd like to consider eliminating the duplicate bin directories and going with a single bin directory like Ant does. Mike > > For another day: > > What about MSYS/MinGW? > If you want your head to explode, try reading http://www.mingw.org/wiki/Posix_path_conversion > > -- Jon > > > On 10/31/2013 01:27 PM, Francis ANDRE wrote: >> Hi Jon >> >> I run all the jdk8 test on WXP/Cygwin with your latest version of jtreg and found this problem: >> >> $ JT_JAVA=/cygdrive/Z/JDK/jdk8/build/windows-x86-normal-server-release/images/j2sdk-image Z:/JDK/jt >> reg/build/images/jtreg/win32/bin/jtreg -J-Xmx512m -vmoption:-Xmx768m -a -ignore:quiet -v:fail,e >> rror,nopass -r:Z:/JDK/jdk8/LANGTO~1/build/WINDOW~1/test/LANGTO~1/jtreg/JTreport >> -w:Z:/JDK/jdk8/LANGTO~1/build/WINDOW~1/test/LANGTO~1/jtreg/JTwork -jdk:/cygdrive/Z/JDK/j >> dk8/build/windows-x86-normal-server-release/images/j2sdk-image -agentvm -concurrency:2 >> . || ( status=$?; if [ $status -ge 3 ]; then exit $status ; fi ; echo $status > Z:/ >> JDK/jdk8/LANGTO~1/build/WINDOW~1/test/LANGTO~1/jtreg/status.txt ) >> Error: JDK not found: \cygdrive\Z\JDK\jdk8\build\windows-x86-normal-server-release\images\j2sdk-imag >> e >> >> The error JDK not found is coming from the replacement of the / by \ in the JT_JAVA environment variable. In effect, the cygwin path should be with "/" and not "\"... -- I know, it is a nightmare --...hopefully,we will beat it! >> >> Francis >> >> Le 31/10/2013 02:41, Jonathan Gibbons a ?crit : >>> Spurred on by the recent discussions and contributions, I've pushed some more changes to the jtreg repo to make it easier to build, and even run most of the tests, on Windows. >>> >>> (I still recommend using Linux instead, when that is an option.) >>> >>> The cygwin world is definitely problematic, especially for running the jtreg tests, since cygwin presents a different view of the file system to the native Windows view seen by Java programs. The problems mostly show up in tests that check that output from jtreg, especially when using diff, grep, etc. For the time being, I've disabled the tests in 11 of the 70 test files in make/tests/*.gmk, meaning that the tests in the remaining 59 files all run successfully. >>> >>> For what its worth, my setup is to have a cygwin symlink from /opt to C:/opt (i.e. /cygdrive/c/opt) which means that I can place all my dependencies in /opt/package/version and can then see them from both the cygwin world and the Windows world, without having to use path-munging utilities like cygpath all over the place. >>> >>> I'm open to more direct support of /cygdrive paths in the build, and wonder if folk have any good tips and tricks for minimising the obtrusiveness of the conversion functions in the composite world of GNU make and cygwin, such that the resulting code runs on Cygwin and POSIX systems. >>> >>> -- Jon >>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.openjdk.java.net/pipermail/jtreg-use/attachments/20131031/183e8ce5/attachment.html