From volker.simonis at gmail.com Tue Jan 14 02:38:10 2014 From: volker.simonis at gmail.com (Volker Simonis) Date: Tue, 14 Jan 2014 11:38:10 +0100 Subject: JDK 8 b121 ea test results are now available In-Reply-To: <52BD4C63.6070509@oracle.com> References: <52BD4C63.6070509@oracle.com> Message-ID: Hi, the tests result page isn't working any more ( http://www.java.net/download/jdk8/testresults/contains an empty html-file while http://www.java.net/download/jdk8/testresults/testresults.html can not be found on the server). This may be related to the java.net outage yesterday. Could you please fix this. Regards, Volker On Fri, Dec 27, 2013 at 10:46 AM, Balchandra Vaidya < balchandra.vaidya at oracle.com> wrote: > > JDK 8 b121 ea test results are now available at: > http://www.java.net/download/jdk8/testresults/testresults.html > > The jdk test results contain 1 difference. > > 0: /home/jtest/merge/b120/jdk/JTwork pass: 4,658; fail: 14; error: 1; not run: 900 > 1: /home/jtest/merge/b121/jdk/JTwork pass: 4,659; fail: 14; not run: 900 > > 0 1 Test > error pass sun/tools/jstatd/TestJstatdExternalRegistry.java > > 1 differences > > The hotspot test results contain 5 differences. > > 0: /home/jtest/merge/b120/hotspot/JTwork pass: 418; fail: 12; error: 2; not run: 7 > 1: /home/jtest/merge/b121/hotspot/JTwork pass: 423; fail: 10; error: 1; not run: 7 > > 0 1 Test > fail pass compiler/7141637/SpreadNullArg.java > --- pass compiler/reflection/ArrayNewInstanceOfVoid.java > error pass compiler/regalloc/C1ObjectSpillInLogicOp.java > fail pass runtime/6925573/SortMethodsTest.java > --- pass runtime/8024804/RegisterNatives.java > > 5 differences > > No differences found in langtools test results. > > No new failures present in Nashorn test result: > > > http://download.java.net/jdk8/testresults/archives/b121/emailable-report.html > > > > Regards > Balchandra > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.openjdk.java.net/pipermail/quality-discuss/attachments/20140114/34065f55/attachment.html From balchandra.vaidya at oracle.com Tue Jan 14 03:28:18 2014 From: balchandra.vaidya at oracle.com (Balchandra Vaidya) Date: Tue, 14 Jan 2014 11:28:18 +0000 Subject: JDK 8 b123 ea test results are now available Message-ID: <52D51F52.3090609@oracle.com> JDK 8 b123 ea test results are now available at: http://www.java.net/download/openjdk/testresults/8/testresults.html The jdk test results contain 10 differences. There is one error which is a testcase issue related to JDK-8028091 . 0: /home/jtest/merge/b121/jdk/JTwork pass: 4,659; fail: 14; not run: 900 1: /home/jtest/merge/b123/jdk/JTwork pass: 4,665; fail: 14; error: 1; not run: 902 0 1 Test --- pass java/net/URLPermission/OpenURL.java --- pass java/util/LinkedHashMap/ComputeIfAbsentAccessOrder.java --- pass javax/xml/jaxp/parsers/8029955/EntityScannerTest.java --- pass sun/security/ssl/com/sun/net/ssl/internal/ssl/SSLContextImpl/CustomizedDefaultProtocols.java --- pass sun/security/ssl/com/sun/net/ssl/internal/ssl/SSLContextImpl/DefaultEnabledProtocols.java --- pass sun/security/ssl/com/sun/net/ssl/internal/ssl/SSLContextImpl/IllegalProtocolProperty.java --- pass sun/security/ssl/com/sun/net/ssl/internal/ssl/SSLContextImpl/NoOldVersionContext.java --- pass sun/security/ssl/com/sun/net/ssl/internal/ssl/SSLContextImpl/SSLContextVersion.java pass --- sun/security/ssl/javax/net/ssl/SSLContextVersion.java pass error sun/tools/jstatd/TestJstatdExternalRegistry.java 10 differences The hotspot test results contain 1 difference. 0: /home/jtest/merge/b121/hotspot/JTwork pass: 423; fail: 10; error: 1; not run: 7 1: /home/jtest/merge/b123/hotspot/JTwork pass: 424; fail: 9; error: 1; not run: 7 0 1 Test fail pass compiler/jsr292/ConcurrentClassLoadingTest.java 1 differences The langtools test results contain 3 differences. 0: /home/jtest/merge/b121/langtools/JTwork pass: 2,962; not run: 7 1: /home/jtest/merge/b123/langtools/JTwork pass: 2,965; not run: 7 0 1 Test --- pass tools/javac/T8029569/VarargsAmbiguityCrashTest.java --- pass tools/javac/lambda/LambdaParenGeneric.java --- pass tools/javac/lambda/LambdaParenGenericOrig.java 3 differences No new failures present in Nashorn test result: http://download.java.net/openjdk/testresults/8/archives/b123/emailable-report.html Regards Balchandra -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.openjdk.java.net/pipermail/quality-discuss/attachments/20140114/ce1b1801/attachment.html From rory.odonnell at oracle.com Tue Jan 14 03:31:31 2014 From: rory.odonnell at oracle.com (Rory O'Donnell Oracle, Dublin Ireland) Date: Tue, 14 Jan 2014 11:31:31 +0000 Subject: JDK 8 b121 ea test results are now available In-Reply-To: References: <52BD4C63.6070509@oracle.com> Message-ID: <52D52013.8010709@oracle.com> Hi Volker, Thanks for letting us know. Balchandra just announced the availability of the latest results for b123. Rgds,Rory On 14/01/2014 10:38, Volker Simonis wrote: > Hi, > > the tests result page isn't working any more > (http://www.java.net/download/jdk8/testresults/ > > contains an empty html-file while > http://www.java.net/download/jdk8/testresults/testresults.html > can > not be found on the server). This may be related to the java.net > outage yesterday. > > Could you please fix this. > > Regards, > Volker > > > > On Fri, Dec 27, 2013 at 10:46 AM, Balchandra Vaidya > > > wrote: > > > JDK 8 b121 ea test results are now available at: > http://www.java.net/download/jdk8/testresults/testresults.html > > The jdk test results contain 1 difference. > > 0: /home/jtest/merge/b120/jdk/JTwork pass: 4,658; fail: 14; error: 1; not run: 900 > 1: /home/jtest/merge/b121/jdk/JTwork pass: 4,659; fail: 14; not run: 900 > > 0 1 Test > error pass sun/tools/jstatd/TestJstatdExternalRegistry.java > > 1 differences > > > The hotspot test results contain 5 differences. > > 0: /home/jtest/merge/b120/hotspot/JTwork pass: 418; fail: 12; error: 2; not run: 7 > 1: /home/jtest/merge/b121/hotspot/JTwork pass: 423; fail: 10; error: 1; not run: 7 > > 0 1 Test > fail pass compiler/7141637/SpreadNullArg.java > --- pass compiler/reflection/ArrayNewInstanceOfVoid.java > error pass compiler/regalloc/C1ObjectSpillInLogicOp.java > fail pass runtime/6925573/SortMethodsTest.java > --- pass runtime/8024804/RegisterNatives.java > > 5 differences > > > No differences found in langtools test results. > > No new failures present in Nashorn test result: > > http://download.java.net/jdk8/testresults/archives/b121/emailable-report.html > > > > Regards > Balchandra > > > -- Rgds,Rory O'Donnell Quality Engineering Manager Oracle EMEA , Dublin, Ireland -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.openjdk.java.net/pipermail/quality-discuss/attachments/20140114/25a46f6f/attachment.html From volker.simonis at gmail.com Tue Jan 14 08:57:48 2014 From: volker.simonis at gmail.com (Volker Simonis) Date: Tue, 14 Jan 2014 17:57:48 +0100 Subject: RFR(S/L): 8028537: PPC64: Updated the JDK regression tests to run on AIX Message-ID: Hi, could you please review the following change: http://cr.openjdk.java.net/~simonis/webrevs/8028537/ which, together with the changes from "8031581: PPC64: Addons and fixes for AIX to pass the jdk regression tests" and "8031134 : PPC64: implement printing on AIX" enables our our port to pass all but the following 7 jtreg regression tests on AIX (compared to the Linux/x86_64 baseline from www.java.net/download/jdk8/testresults/testresults.html?): java/net/Inet6Address/B6558853.java java/nio/channels/AsynchronousChannelGroup/Basic.java (sporadically) java/nio/channels/AsynchronousChannelGroup/GroupOfOne.java java/nio/channels/AsynchronousChannelGroup/Unbounded.java (sporadically) java/nio/channels/Selector/RacyDeregister.java sun/security/krb5/auto/Unreachable.java (only on IPv6) The change is only big in the amount of files it touches but rather small in the amount of actual code changes so I flagged it with S/L. Most changes simply add AIX as a known platform to the OS detection sections of the various tests. The are either of the form: case "$OS" in - SunOS | Linux | Darwin ) + SunOS | Linux | Darwin | AIX ) PATHSEP=":" or: isSolaris=true ;; + AIX ) + OS="AIX" + isAIX=true + ;; Windows* ) OS="Windows" The following explanations only mention test with changes different to the ones above: test/ProblemList.txt - Added three tests which currently don't work on AIX. test/com/sun/java/swing/plaf/windows/8016551/bug8016551.java - This test calls JFrame.setDefaultCloseOperation() which is not allowed under the security manager which is active if the test are running in agentvm mode. So better always run this test in othervm mode. test/com/sun/jdi/PrivateTransportTest.sh - On AIX, we have to use LIBPATH instead of LD_LIBRARY_PATH. test/com/sun/nio/sctp/SctpChannel/Util.java test/com/sun/nio/sctp/SctpMultiChannel/Util.java test/com/sun/nio/sctp/SctpServerChannel/Util.java - On AIX, we currently haven't implemented SCTP but we nevertheless compile the shared SCTP classes into the runtime class library. This way the AIX JDK can at least compile SCTP applications altough it can not run them. To support this scenario, the runtime check for the availability of SCTP has to be extended to catch UnsatisfiedLinkError and NoClassDefFoundError. UnsatisfiedLinkError will be thrown the first time when the class SctpChannelImpl will be loaded because it cannot load the its native support library in the static initialisation section. On the next load attempt of the class, a NoClassDefFoundError will be thrown because of the previously failed initialisation. test/java/net/DatagramSocket/Send12k.java - AIX throws an IOException: Message too long if the message is too long. DatagramSocket.send() is specified to throw an IOException so better don't be too specific in the catch clause. test/java/nio/file/Files/SBC.java - AIX actually supports symbolic links, but it does not support NOFOLLOW_LINKS, or more exactly the O_NOFOLLOW flag to the open() system call which is tested here. test/java/nio/file/Files/walkFileTree/find.sh - On AIX find -follow may core dump on recursive links without '-L' (see http://www-01.ibm.com/support/docview.wss?uid=isg1IV28143). test/java/util/logging/AnonLoggerWeakRefLeak.sh test/java/util/logging/LoggerWeakRefLeak.sh - Only treat missing jmap options as warnings and not as errors. test/sun/rmi/rmic/newrmic/equivalence/batch.sh - On AIX the diff utility doesn't detect binary files and thus outputs the full diff of different class files which makes the test fail. Because the generated class files aren?t used or checked anyway we can completely omit the generation of class files by always using the -nowrite option. - Also reformatted the command lines to make the differences more apparent. test/tools/launcher/ExecutionEnvironment.java - On AIX, we have to use LIBPATH instead of LD_LIBRARY_PATH. - AIX does not support the -rpath linker options so the launchers have to prepend the jdk library path to LIBPATH. test/tools/launcher/Settings.java - On PPC64 we need a bigger stack size. Thank you and best regards, Volker -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.openjdk.java.net/pipermail/quality-discuss/attachments/20140114/0c97a9bc/attachment-0001.html From balchandra.vaidya at oracle.com Tue Jan 14 09:59:14 2014 From: balchandra.vaidya at oracle.com (Balchandra Vaidya) Date: Tue, 14 Jan 2014 17:59:14 +0000 Subject: JDK 7u60 b02 ea test results are now available Message-ID: <52D57AF2.1070203@oracle.com> JDK 7u60 b02 update release test results are now available at http://www.java.net/download/openjdk/testresults/7/testresults.html The results contain no new test failure when compared with 7u60 b01 test results. Thanks Balchandra From Alan.Bateman at oracle.com Tue Jan 14 11:13:25 2014 From: Alan.Bateman at oracle.com (Alan Bateman) Date: Tue, 14 Jan 2014 19:13:25 +0000 Subject: RFR(S/L): 8028537: PPC64: Updated the JDK regression tests to run on AIX In-Reply-To: References: Message-ID: <52D58C55.6070004@oracle.com> On 14/01/2014 16:57, Volker Simonis wrote: > : > > test/com/sun/nio/sctp/SctpChannel/Util.java > test/com/sun/nio/sctp/SctpMultiChannel/Util.java > test/com/sun/nio/sctp/SctpServerChannel/Util.java > > - On AIX, we currently haven't implemented SCTP but we nevertheless > compile the shared SCTP classes into the runtime class library. This way > the AIX JDK can at least compile SCTP applications altough it can not run > them. To support this scenario, the runtime check for the availability of > SCTP has to be extended to catch UnsatisfiedLinkError and > NoClassDefFoundError. UnsatisfiedLinkError will be thrown the first time > when the class SctpChannelImpl will be loaded because it cannot load the > its native support library in the static initialisation section. On the > next load attempt of the class, a NoClassDefFoundError will be thrown > because of the previously failed initialisation. > OS X has the same issue and the solution used there are stub implementations that just throw UOE. Details in jdk/src/macosx/classes/sun/nio/ch/sctp and that maybe that would work for AIX too. -Alan. From volker.simonis at gmail.com Wed Jan 15 08:42:47 2014 From: volker.simonis at gmail.com (Volker Simonis) Date: Wed, 15 Jan 2014 17:42:47 +0100 Subject: RFR(S/L): 8028537: PPC64: Updated the JDK regression tests to run on AIX In-Reply-To: <52D58C55.6070004@oracle.com> References: <52D58C55.6070004@oracle.com> Message-ID: Hi Alan, thanks for the suggestion. That's fine for me. I've copied the empty SCTP stubs from the macosx to the aix directory as well and updated the make file accordingly (in the patch for "8031581: PPC64: Addons and fixes for AIX to pass the jdk regression tests"). Therefore, the changes to the three tests: test/com/sun/nio/sctp/SctpChannel/Util.java test/com/sun/nio/sctp/SctpMultiChannel/Util.java test/com/sun/nio/sctp/SctpServerChannel/Util.java can be considered obsolete. Regards, Volker On Tue, Jan 14, 2014 at 8:13 PM, Alan Bateman wrote: > On 14/01/2014 16:57, Volker Simonis wrote: > >> : >> >> test/com/sun/nio/sctp/SctpChannel/Util.java >> test/com/sun/nio/sctp/SctpMultiChannel/Util.java >> test/com/sun/nio/sctp/SctpServerChannel/Util.java >> >> - On AIX, we currently haven't implemented SCTP but we nevertheless >> >> compile the shared SCTP classes into the runtime class library. This >> way >> the AIX JDK can at least compile SCTP applications altough it can not >> run >> them. To support this scenario, the runtime check for the >> availability of >> SCTP has to be extended to catch UnsatisfiedLinkError and >> NoClassDefFoundError. UnsatisfiedLinkError will be thrown the first >> time >> when the class SctpChannelImpl will be loaded because it cannot load >> the >> its native support library in the static initialisation section. On >> the >> next load attempt of the class, a NoClassDefFoundError will be thrown >> because of the previously failed initialisation. >> >> OS X has the same issue and the solution used there are stub > implementations that just throw UOE. Details in jdk/src/macosx/classes/sun/nio/ch/sctp > and that maybe that would work for AIX too. > > -Alan. > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.openjdk.java.net/pipermail/quality-discuss/attachments/20140115/332896b9/attachment.html From Alan.Bateman at oracle.com Fri Jan 17 01:48:46 2014 From: Alan.Bateman at oracle.com (Alan Bateman) Date: Fri, 17 Jan 2014 09:48:46 +0000 Subject: RFR(S/L): 8028537: PPC64: Updated the JDK regression tests to run on AIX In-Reply-To: References: <52D58C55.6070004@oracle.com> Message-ID: <52D8FC7E.5080908@oracle.com> On 15/01/2014 16:42, Volker Simonis wrote: > Hi Alan, > > thanks for the suggestion. That's fine for me. I've copied the empty > SCTP stubs from the macosx to the aix directory as well and updated > the make file accordingly (in the patch for "8031581: PPC64: Addons > and fixes for AIX to pass the jdk regression tests"). > > Therefore, the changes to the three tests: > > test/com/sun/nio/sctp/SctpChannel/Util.java > test/com/sun/nio/sctp/SctpMultiChannel/Util.java > test/com/sun/nio/sctp/SctpServerChannel/Util.java > > can be considered obsolete. Thanks, I think this makes the most sense. I looked through the rest of this webrev and the update to the tests looks fine. One general comment is that for many of these shell tests (that survive the current effort to replace them) is that we could move the Unix handling into the match any case so that we don't have to list each of Linux, SunOS, Darwin, ... I think this came up when the OS X port was brought in but there wasn't any follow-up on it. I am not suggesting you do this here, it's just a comment as I see same change to so many tests. A minor comment on SBC.java is that it could just catch UnsupportedOperationException on L238, that would avoid needing to check os.name. A really minor comment on the updates to ProblemList.txt is that the JMX test should probably be in the jdk_jmx section (it's just a convention that we've been using, it doesn't of course really matter where tests are listed). -Alan From Alan.Bateman at oracle.com Fri Jan 17 07:50:27 2014 From: Alan.Bateman at oracle.com (Alan Bateman) Date: Fri, 17 Jan 2014 15:50:27 +0000 Subject: RFR(S/L): 8028537: PPC64: Updated the JDK regression tests to run on AIX In-Reply-To: References: Message-ID: <52D95143.6080601@oracle.com> On 14/01/2014 16:57, Volker Simonis wrote: > Hi, > > could you please review the following change: > > http://cr.openjdk.java.net/~simonis/webrevs/8028537/ > > which, together with the changes from "8031581: PPC64: Addons and fixes for > AIX to pass the jdk regression tests" and "8031134 : PPC64: implement > printing on AIX" enables our our port to pass all but the following 7 jtreg > regression tests on AIX (compared to the Linux/x86_64 baseline from > www.java.net/download/jdk8/testresults/testresults.html?): > I've finally got to this one. As the event translation issue is now a separate issue then I've ignored that part. I'm not comfortable with the changes to FileDispatcherImpl.c as I don't think we shouldn't be calling into IO_ or NET_* functions here. I think I get the issue that you have on AIX (and assume it's the preClose/dup2 that blocks rather than close) but need a bit of time to suggest alternatives. It may be that it will require an AIX specific SocketDispatcher. Do you happen to know which tests fail due to this part? The other changes look okay. There is a typo in the change to zip_util.c, s/legel/legal/. In DatagramChannelImpl.c then you handle connect failing with EAFNOSUPPORT. I would be tempted to replace the comment to say that it EAFNOSUPPORT can be ignored on AIX. A minor comment but the indentation for rv = errno can be fixed (I see the BSD code has it wrong too). -Alan. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.openjdk.java.net/pipermail/quality-discuss/attachments/20140117/74d15d2f/attachment.html From volker.simonis at gmail.com Fri Jan 17 13:10:22 2014 From: volker.simonis at gmail.com (Volker Simonis) Date: Fri, 17 Jan 2014 22:10:22 +0100 Subject: RFR(S/L): 8028537: PPC64: Updated the JDK regression tests to run on AIX In-Reply-To: <52D8FC7E.5080908@oracle.com> References: <52D58C55.6070004@oracle.com> <52D8FC7E.5080908@oracle.com> Message-ID: Hi Alan, thanks for looking at this. Please find may comments inline: On Fri, Jan 17, 2014 at 10:48 AM, Alan Bateman wrote: > On 15/01/2014 16:42, Volker Simonis wrote: >> >> Hi Alan, >> >> thanks for the suggestion. That's fine for me. I've copied the empty SCTP >> stubs from the macosx to the aix directory as well and updated the make file >> accordingly (in the patch for "8031581: PPC64: Addons and fixes for AIX to >> pass the jdk regression tests"). >> >> Therefore, the changes to the three tests: >> >> test/com/sun/nio/sctp/SctpChannel/Util.java >> test/com/sun/nio/sctp/SctpMultiChannel/Util.java >> test/com/sun/nio/sctp/SctpServerChannel/Util.java >> >> can be considered obsolete. > > Thanks, I think this makes the most sense. > > I looked through the rest of this webrev and the update to the tests looks > fine. > Great, thanks. > One general comment is that for many of these shell tests (that survive the > current effort to replace them) is that we could move the Unix handling into > the match any case so that we don't have to list each of Linux, SunOS, > Darwin, ... I think this came up when the OS X port was brought in but > there wasn't any follow-up on it. I am not suggesting you do this here, it's > just a comment as I see same change to so many tests. > > A minor comment on SBC.java is that it could just catch > UnsupportedOperationException on L238, that would avoid needing to check > os.name. > I agree, that looks much nicer. Done as requested. > A really minor comment on the updates to ProblemList.txt is that the JMX > test should probably be in the jdk_jmx section (it's just a convention that > we've been using, it doesn't of course really matter where tests are > listed). Done. Moved the excluded tests down to the jdk_jmx section. Here's the new webrev: http://cr.openjdk.java.net/~simonis/webrevs/8028537_2/ Can I push this now to ppc-aix-port/stage-9? Thank you and best regards, Volker > > -Alan From Alan.Bateman at oracle.com Fri Jan 17 13:24:56 2014 From: Alan.Bateman at oracle.com (Alan Bateman) Date: Fri, 17 Jan 2014 21:24:56 +0000 Subject: RFR(S/L): 8028537: PPC64: Updated the JDK regression tests to run on AIX In-Reply-To: References: <52D58C55.6070004@oracle.com> <52D8FC7E.5080908@oracle.com> Message-ID: <52D99FA8.1060108@oracle.com> On 17/01/2014 21:10, Volker Simonis wrote: > : > Done. Moved the excluded tests down to the jdk_jmx section. > > Here's the new webrev: > > http://cr.openjdk.java.net/~simonis/webrevs/8028537_2/ > > Can I push this now to ppc-aix-port/stage-9? > The SBC change looks good. I can't see the move of the excluded test but it's not important anyway. So I think this one is good to go. -Alan. From martijnverburg at gmail.com Sat Jan 18 05:29:18 2014 From: martijnverburg at gmail.com (Martijn Verburg) Date: Sat, 18 Jan 2014 13:29:18 +0000 Subject: jtreg nightly build version change Message-ID: Hi all, https://adopt-openjdk.ci.cloudbees.com/job/jtreg/lastSuccessfulBuild/artifact/now produces a Maven compatible 5.0.0-SNAPSHOT version of jtreg. This was to make the download and install for the Virtual Machines we're producing for the build-farm as well as making jtreg Maven repo compatible. IIRC jtreg was last released as version 4.3? Hopefully 5.0.0 is the next logical number. Probably needs a conversation about how to deal with versioning and if jtreg can be uploaded to Maven Central or not (any legal barriers?). Cheers, Martijn -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.openjdk.java.net/pipermail/quality-discuss/attachments/20140118/68d16b19/attachment.html From sadhak001 at gmail.com Sat Jan 18 05:34:01 2014 From: sadhak001 at gmail.com (Mani Sarkar) Date: Sat, 18 Jan 2014 13:34:01 +0000 Subject: jtreg nightly build version change In-Reply-To: References: Message-ID: Correct link is https://adopt-openjdk.ci.cloudbees.com/job/jtreg/lastSuccessfulBuild/artifact/ the now at the end of it was a separate word. Thanks Martijn. Cheers, Mani On Sat, Jan 18, 2014 at 1:29 PM, Martijn Verburg wrote: > Hi all, > > > https://adopt-openjdk.ci.cloudbees.com/job/jtreg/lastSuccessfulBuild/artifact/now > produces a Maven compatible 5.0.0-SNAPSHOT version of jtreg. > > This was to make the download and install for the Virtual Machines we're > producing for the build-farm as well as making jtreg Maven repo compatible. > > IIRC jtreg was last released as version 4.3? Hopefully 5.0.0 is the next > logical number. > > Probably needs a conversation about how to deal with versioning and if > jtreg can be uploaded to Maven Central or not (any legal barriers?). > > Cheers, > Martijn > -- *Twitter:* @theNeomatrix369 *Blog:* http://neomatrix369.wordpress.com *JUG activity: *LJC Associate & LJC Advocate (@adoptopenjdk & @adoptajsr programs) *Meet-a-Project:* https://github.com/MutabilityDetector *Bitbucket:* https://bitbucket.org/neomatrix369 *Github:* https://github .com/neomatrix369 *LinkedIn:* http://uk.linkedin.com/pub/mani-sarkar/71/a77/39b *Don't chase success, rather aim for "Excellence", and success will come chasing after you!* -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.openjdk.java.net/pipermail/quality-discuss/attachments/20140118/fddb54df/attachment.html From jonathan.gibbons at oracle.com Mon Jan 20 09:47:21 2014 From: jonathan.gibbons at oracle.com (Jonathan Gibbons) Date: Mon, 20 Jan 2014 09:47:21 -0800 Subject: jtreg nightly build version change In-Reply-To: References: Message-ID: <52DD6129.1010703@oracle.com> On 01/18/2014 05:29 AM, Martijn Verburg wrote: > Hi all, > > https://adopt-openjdk.ci.cloudbees.com/job/jtreg/lastSuccessfulBuild/artifact/ > now produces a Maven compatible 5.0.0-SNAPSHOT version of jtreg. > > This was to make the download and install for the Virtual Machines > we're producing for the build-farm as well as making jtreg Maven repo > compatible. > > IIRC jtreg was last released as version 4.3? Hopefully 5.0.0 is the > next logical number. > > Probably needs a conversation about how to deal with versioning and if > jtreg can be uploaded to Maven Central or not (any legal barriers?). > > Cheers, > Martijn Martijn, jtreg has never been 4.3. I think you're confusing it with the version of JTHarness that it uses. For a while now, jtreg has been using jtreg 4.1 bNN where NN is a small interger, currently 08. This was more significant when we (Oracle) were producing binary builds. Now that we are no longer doing that, I think we will start advancing the jtreg number in a more conventional fashion. I had hoped to combine the advance to 4.2 with a major update to the jtreg documentation, but that seems to be never quite high enough priority to have anything happen :-( -- Jon From martijnverburg at gmail.com Mon Jan 20 09:54:04 2014 From: martijnverburg at gmail.com (Martijn Verburg) Date: Mon, 20 Jan 2014 17:54:04 +0000 Subject: jtreg nightly build version change In-Reply-To: <52DD6129.1010703@oracle.com> References: <52DD6129.1010703@oracle.com> Message-ID: Hi Jonathan, Thanks for the info. In that case I'll change the build to produce a 4.2.0-SNAPSHOT following the traditional model. I guess we can then work on the build script to allow it to produce formal releases (such as 4.2.0) to Maven central. I don't have permission to raise an issue directly in JBUG for this, are you able to or does it still need to go through the bugs.sun... method? Cheers, Martijn On 20 January 2014 17:47, Jonathan Gibbons wrote: > On 01/18/2014 05:29 AM, Martijn Verburg wrote: > >> Hi all, >> >> https://adopt-openjdk.ci.cloudbees.com/job/jtreg/ >> lastSuccessfulBuild/artifact/ now produces a Maven compatible >> 5.0.0-SNAPSHOT version of jtreg. >> >> This was to make the download and install for the Virtual Machines we're >> producing for the build-farm as well as making jtreg Maven repo compatible. >> >> IIRC jtreg was last released as version 4.3? Hopefully 5.0.0 is the next >> logical number. >> >> Probably needs a conversation about how to deal with versioning and if >> jtreg can be uploaded to Maven Central or not (any legal barriers?). >> >> Cheers, >> Martijn >> > > Martijn, > > jtreg has never been 4.3. I think you're confusing it with the version of > JTHarness that it uses. > > For a while now, jtreg has been using jtreg 4.1 bNN where NN is a small > interger, currently 08. This was more significant when we (Oracle) were > producing binary builds. Now that we are no longer doing that, I think we > will start advancing the jtreg number in a more conventional fashion. > > I had hoped to combine the advance to 4.2 with a major update to the jtreg > documentation, but that seems to be never quite high enough priority to > have anything happen :-( > > -- Jon > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.openjdk.java.net/pipermail/quality-discuss/attachments/20140120/aff0d803/attachment.html From martijnverburg at gmail.com Mon Jan 20 09:54:06 2014 From: martijnverburg at gmail.com (Martijn Verburg) Date: Mon, 20 Jan 2014 17:54:06 +0000 Subject: jtreg nightly build version change In-Reply-To: <52DD6129.1010703@oracle.com> References: <52DD6129.1010703@oracle.com> Message-ID: Hi Jonathan, Thanks for the info. In that case I'll change the build to produce a 4.2.0-SNAPSHOT following the traditional model. I guess we can then work on the build script to allow it to produce formal releases (such as 4.2.0) to Maven central. I don't have permission to raise an issue directly in JBUG for this, are you able to or does it still need to go through the bugs.sun... method? Cheers, Martijn On 20 January 2014 17:47, Jonathan Gibbons wrote: > On 01/18/2014 05:29 AM, Martijn Verburg wrote: > >> Hi all, >> >> https://adopt-openjdk.ci.cloudbees.com/job/jtreg/ >> lastSuccessfulBuild/artifact/ now produces a Maven compatible >> 5.0.0-SNAPSHOT version of jtreg. >> >> This was to make the download and install for the Virtual Machines we're >> producing for the build-farm as well as making jtreg Maven repo compatible. >> >> IIRC jtreg was last released as version 4.3? Hopefully 5.0.0 is the next >> logical number. >> >> Probably needs a conversation about how to deal with versioning and if >> jtreg can be uploaded to Maven Central or not (any legal barriers?). >> >> Cheers, >> Martijn >> > > Martijn, > > jtreg has never been 4.3. I think you're confusing it with the version of > JTHarness that it uses. > > For a while now, jtreg has been using jtreg 4.1 bNN where NN is a small > interger, currently 08. This was more significant when we (Oracle) were > producing binary builds. Now that we are no longer doing that, I think we > will start advancing the jtreg number in a more conventional fashion. > > I had hoped to combine the advance to 4.2 with a major update to the jtreg > documentation, but that seems to be never quite high enough priority to > have anything happen :-( > > -- Jon > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.openjdk.java.net/pipermail/quality-discuss/attachments/20140120/8669ccc2/attachment.html From jonathan.gibbons at oracle.com Tue Jan 21 08:37:25 2014 From: jonathan.gibbons at oracle.com (Jonathan Gibbons) Date: Tue, 21 Jan 2014 08:37:25 -0800 Subject: jtreg nightly build version change In-Reply-To: References: <52DD6129.1010703@oracle.com> Message-ID: <52DEA245.9050303@oracle.com> Martin, Right now, the latest tag in the repo should be jtreg4.1-b08. It seems to be it would be good if your build could reflect that. There should be enough hooks in the build script to allow you to set the version. -- Jon On 01/20/2014 09:54 AM, Martijn Verburg wrote: > Hi Jonathan, > > Thanks for the info. In that case I'll change the build to produce a > 4.2.0-SNAPSHOT following the traditional model. I guess we can then > work on the build script to allow it to produce formal releases (such > as 4.2.0) to Maven central. > > I don't have permission to raise an issue directly in JBUG for this, > are you able to or does it still need to go through the bugs.sun... > method? > > > > Cheers, > Martijn > > > On 20 January 2014 17:47, Jonathan Gibbons > > wrote: > > On 01/18/2014 05:29 AM, Martijn Verburg wrote: > > Hi all, > > https://adopt-openjdk.ci.cloudbees.com/job/jtreg/lastSuccessfulBuild/artifact/ > now produces a Maven compatible 5.0.0-SNAPSHOT version of jtreg. > > This was to make the download and install for the Virtual > Machines we're producing for the build-farm as well as making > jtreg Maven repo compatible. > > IIRC jtreg was last released as version 4.3? Hopefully 5.0.0 > is the next logical number. > > Probably needs a conversation about how to deal with > versioning and if jtreg can be uploaded to Maven Central or > not (any legal barriers?). > > Cheers, > Martijn > > > Martijn, > > jtreg has never been 4.3. I think you're confusing it with the > version of JTHarness that it uses. > > For a while now, jtreg has been using jtreg 4.1 bNN where NN is a > small interger, currently 08. This was more significant when we > (Oracle) were producing binary builds. Now that we are no longer > doing that, I think we will start advancing the jtreg number in a > more conventional fashion. > > I had hoped to combine the advance to 4.2 with a major update to > the jtreg documentation, but that seems to be never quite high > enough priority to have anything happen :-( > > -- Jon > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.openjdk.java.net/pipermail/quality-discuss/attachments/20140121/6d968f53/attachment.html From balchandra.vaidya at oracle.com Wed Jan 22 04:05:19 2014 From: balchandra.vaidya at oracle.com (Balchandra Vaidya) Date: Wed, 22 Jan 2014 12:05:19 +0000 Subject: JDK 8 b124 ea test results are now available Message-ID: <52DFB3FF.60601@oracle.com> JDK 8 b124 ea test results are now available at: http://www.java.net/download/openjdk/testresults/8/testresults.html The jdk test results contain 8 differences from b123 test results. No new failure found. 0: /home/jtest/merge/b123/jdk/JTwork pass: 4,665; fail: 14; error: 1; not run: 902 1: /home/jtest/merge/b124/jdk/JTwork pass: 4,673; fail: 14; not run: 902 0 1 Test --- pass java/lang/System/SetPropertiesNull.java --- pass java/lang/invoke/ObjectMethodInInterfaceTest.java --- pass java/util/logging/RootLogger/RootLevelInConfigFile.java --- pass java/util/stream/test/org/openjdk/tests/java/util/stream/CountLargeTest.java --- pass java/util/stream/test/org/openjdk/tests/java/util/stream/CountTest.java --- pass sun/security/tools/jarsigner/warnings.sh error pass sun/tools/jstatd/TestJstatdExternalRegistry.java --- pass sun/util/resources/TimeZone/TimeZoneNames/TimeZoneNamesTest.java 8 differences The hotspot and langtool test results have no difference from b123 test results. No new failure present in Nashorn test result: http://download.java.net/openjdk/testresults/8/archives/b124/emailable-report.html Regards Balchandra -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.openjdk.java.net/pipermail/quality-discuss/attachments/20140122/4449c8eb/attachment.html From balchandra.vaidya at oracle.com Wed Jan 22 04:26:35 2014 From: balchandra.vaidya at oracle.com (Balchandra Vaidya) Date: Wed, 22 Jan 2014 12:26:35 +0000 Subject: JDK 7u60 b03 ea test results are now available Message-ID: <52DFB8FB.2010406@oracle.com> JDK 7u60 b03 update release test results are now available at http://www.java.net/download/openjdk/testresults/7/testresults.html The jdk test results contain 6 differences and 2 new failures from 7u60 b02 test results. 0: /home/jtest/merge7/jdk7u60-b02/jdk/JTwork pass: 3,910; fail: 13; not run: 814 1: /home/jtest/merge7/jdk7u60-b03/jdk/JTwork pass: 3,912; fail: 14; not run: 814 0 1 Test pass fail java/beans/Introspector/TestTypeResolver.java --- pass java/lang/Class/checkMemberAccess/CheckMemberAccess.java --- pass java/lang/ref/FinalizeOverride.java pass fail java/rmi/activation/Activatable/forceLogSnapshot/ForceLogSnapshot.java fail pass javax/xml/ws/clientjar/TestWsImport.java --- pass sun/security/tools/jarsigner/warnings.sh 6 differences Both failures are testcase issues and are under investigation. The hotspot test results contain 2 differences. 1: /home/jtest/merge7/jdk7u60-b03/hotspot/JTwork pass: 266; fail: 5; not run: 2 0 1 Test --- pass compiler/reflection/ArrayNewInstanceOfVoid.java --- pass gc/6941923/test6941923.sh 2 differences The langtools test results contain no difference from 7u60 b02 test results. Thanks Balchandra -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.openjdk.java.net/pipermail/quality-discuss/attachments/20140122/ff376c4c/attachment.html From balchandra.vaidya at oracle.com Tue Jan 28 02:50:47 2014 From: balchandra.vaidya at oracle.com (Balchandra Vaidya) Date: Tue, 28 Jan 2014 10:50:47 +0000 Subject: JDK 7u60 b04 ea test results are now available Message-ID: <52E78B87.5000102@oracle.com> JDK 7u60 b04 update release test results are now available at http://www.java.net/download/openjdk/testresults/7/testresults.html Overall test results contain no new test failures. The jdk test results contain 4 differences from 7u60 b03 test results. 0: /home/jtest/merge7/jdk7u60-b03/jdk/JTwork pass: 3,912; fail: 14; not run: 814 1: /home/jtest/merge7/jdk7u60-b04/jdk/JTwork pass: 3,916; fail: 13; not run: 814 0 1 Test --- pass java/lang/invoke/8009222/Test8009222.java fail pass java/rmi/activation/Activatable/forceLogSnapshot/ForceLogSnapshot.java --- pass java/util/logging/TestLoggingWithMainAppContext.java --- pass java/util/logging/TestMainAppContext.java 4 differences The hotspot test results contain 1 difference. 0: /home/jtest/merge7/jdk7u60-b03/hotspot/JTwork pass: 266; fail: 5; not run: 2 1: /home/jtest/merge7/jdk7u60-b04/hotspot/JTwork pass: 267; fail: 5; not run: 2 0 1 Test --- pass runtime/jsig/Test8017498.sh 1 differences The langtools test results contain no difference from 7u60 b03 test results. Thanks Balchandra -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.openjdk.java.net/pipermail/quality-discuss/attachments/20140128/a4f3259d/attachment.html From balchandra.vaidya at oracle.com Fri Jan 31 01:43:04 2014 From: balchandra.vaidya at oracle.com (Balchandra Vaidya) Date: Fri, 31 Jan 2014 09:43:04 +0000 Subject: JDK 8 b126 ea test results are now available Message-ID: <52EB7028.3060808@oracle.com> JDK 8 b126 ea test results are now available at: http://www.java.net/download/openjdk/testresults/8/testresults.html The test results are identical to b124 test results. No new failure present in Nashorn test result: http://download.java.net/openjdk/testresults/8/archives/b126/emailable-report.html Regards Balchandra -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.openjdk.java.net/pipermail/quality-discuss/attachments/20140131/0b011cc7/attachment.html