From abdul.kolarkunnu at oracle.com Wed Feb 1 14:17:42 2017 From: abdul.kolarkunnu at oracle.com (Muneer Kolarkunnu) Date: Wed, 1 Feb 2017 06:17:42 -0800 (PST) Subject: JDK 9 build 154 test results now available Message-ID: <4dd93ef0-dc95-4ab0-a6e2-dc5d4ef380ca@default> JDK 9 ea build 154 test results are now available at http://www.java.net/download/openjdk/testresults/9/testresults.html The jdk test results contain 9 differences from the build 153 test results. No new testcase failures found. 0: /home/jtest/merge9/153/jdk/JTwork pass: 6,130; fail: 9; not run: 2,238 1: /home/jtest/merge9/154/jdk/JTwork pass: 6,137; fail: 9; not run: 2,240 0 1 Test --- pass java/rmi/MarshalledObject/MOFilterTest.java --- pass java/rmi/registry/serialFilter/RegistryFilterTest.java --- pass java/util/logging/modules/LogManagerInModule/LogManagerInModuleTest.java --- pass sun/management/LoggingTest/LoggingWithJULTest.java --- pass sun/management/LoggingTest/LoggingWithLoggerFinderTest.java --- pass sun/security/tools/keytool/ImportPrompt.java --- pass tools/jar/multiRelease/ApiValidatorTest.java pass --- tools/jlink/CustomPluginTest.java --- pass tools/jlink/ResourceDuplicateCheckTest.java 9 difference The hotspot test results contain 0 differences from the build 153 test results. The langtools test results contain 6 differences from the build 153 test results. No new testcase failures found. 0: /home/jtest/merge9/153/langtools/JTwork pass: 3,550; not run: 299 1: /home/jtest/merge9/154/langtools/jtreg/JTwork pass: 3,556; not run: 301 0 1 Test --- pass tools/javac/annotations/neg/8171322/TypeVariableAsAnnotationTest.java --- pass tools/javac/classreader/FileSystemClosedTest.java --- pass tools/javac/modules/IncubatingTest.java --- pass tools/javac/modules/ModulesAndModuleSourcePathTest.java --- pass tools/javac/processing/model/TestVisitorDefaults.java --- pass tools/javadoc/TestScriptInComment.java 6 differences The nashorn test result is available at http://download.java.net/openjdk/testresults/9/archives/154/emailable-report.html -- Regards, Abdul Muneer Quality Engineer Oracle, Bangalore, India -------------- next part -------------- An HTML attachment was scrubbed... URL: From rory.odonnell at oracle.com Fri Feb 3 21:17:00 2017 From: rory.odonnell at oracle.com (Rory O'Donnell) Date: Fri, 3 Feb 2017 21:17:00 +0000 Subject: JDK 9 EA Build 155 is available on java.net Message-ID: Hi All, *JDK 9 Early Access* b155 is available on java.net There have been a number of fixes to bugs reported by Open Source projects since the last availability email : * b155 - JDK-8167273 : Calendar.getDisplayNames inconsistent with DateFormatSymbols * b154 - JDK-8157611 : field visiblePackages is null for the unnamed module producing NPE when accessed * b153 - JDK-8163449 : Allow per protocol setting for URLConnection defaultUseCaches * b152 - JDK-8172158 : Annotation processor not run with -source <= 8 Dalibor and I are presenting at FOSDEM this weekend, we would love to meet you there! * JDK 9 Outreach - The Awesome Parts Rgds,Rory -- Rgds,Rory O'Donnell Quality Engineering Manager Oracle EMEA , Dublin, Ireland -------------- next part -------------- An HTML attachment was scrubbed... URL: From jerboaa at gmail.com Sat Feb 4 16:51:11 2017 From: jerboaa at gmail.com (Severin Gehwolf) Date: Sat, 4 Feb 2017 17:51:11 +0100 Subject: Please add project Thermostat to quality outreach program Message-ID: Hi, We'd like to have Thermostat[1] added to the quality outreach program. I'm one of the Thermostat developers and we've already started testing Thermostat on JDK 9. Current status is here: http://icedtea.classpath.org/bugzilla/show_bug.cgi?id=2157 Cheers, Severin [1] http://icedtea.classpath.org/thermostat/ From rory.odonnell at oracle.com Sun Feb 5 12:33:39 2017 From: rory.odonnell at oracle.com (Rory O'Donnell) Date: Sun, 5 Feb 2017 13:33:39 +0100 Subject: Please add project Thermostat to quality outreach program In-Reply-To: References: Message-ID: <0f22e32a-d53b-b20c-e602-4df57cab790c@oracle.com> Hi Severin, Nice to meet you at FOSDEM. To list Thermostat on the wiki [1] can you provide a contact name, the current status of you testing against JDK 8 & JDK 9, and a CI if possible ? Rgds,Rory [1] https://wiki.openjdk.java.net/display/quality/Quality+Outreach On 04/02/2017 17:51, Severin Gehwolf wrote: > Hi, > > We'd like to have Thermostat[1] added to the quality outreach program. > I'm one of the Thermostat developers and we've already started testing > Thermostat on JDK 9. > > Current status is here: > http://icedtea.classpath.org/bugzilla/show_bug.cgi?id=2157 > > Cheers, > Severin > > [1] http://icedtea.classpath.org/thermostat/ -- Rgds,Rory O'Donnell Quality Engineering Manager Oracle EMEA, Dublin,Ireland From jerboaa at gmail.com Tue Feb 7 15:29:35 2017 From: jerboaa at gmail.com (Severin Gehwolf) Date: Tue, 7 Feb 2017 16:29:35 +0100 Subject: Please add project Thermostat to quality outreach program In-Reply-To: <0f22e32a-d53b-b20c-e602-4df57cab790c@oracle.com> References: <0f22e32a-d53b-b20c-e602-4df57cab790c@oracle.com> Message-ID: Hi Rory, On Sun, Feb 5, 2017 at 1:33 PM, Rory O'Donnell wrote: > Hi Severin, > > Nice to meet you at FOSDEM. Likewise. > To list Thermostat on the wiki [1] can you provide a contact name, the > current status of you testing against JDK 8 & JDK 9, and a CI if possible ? You can list me as contact. We do have CI for JDK 8 which is passing, but it's set up on a non-public instance currently. We don't do JDK 9 based CI at this point. The current status of JDK 9 compatibility is that we've tried building and running Thermostat on JDK 9, but that has been a while ago now since we've last tried. The next couple of months this will be a higher priority given the JDK 9 GA timeline. The plan is to be JDK 9 compatible when it GAs. Thanks, Severin > Rgds,Rory > > [1] https://wiki.openjdk.java.net/display/quality/Quality+Outreach > > > On 04/02/2017 17:51, Severin Gehwolf wrote: >> >> Hi, >> >> We'd like to have Thermostat[1] added to the quality outreach program. >> I'm one of the Thermostat developers and we've already started testing >> Thermostat on JDK 9. >> >> Current status is here: >> http://icedtea.classpath.org/bugzilla/show_bug.cgi?id=2157 >> >> Cheers, >> Severin >> >> [1] http://icedtea.classpath.org/thermostat/ > > > -- > Rgds,Rory O'Donnell > Quality Engineering Manager > Oracle EMEA, Dublin,Ireland > From rory.odonnell at oracle.com Tue Feb 7 16:41:33 2017 From: rory.odonnell at oracle.com (Rory O'Donnell) Date: Tue, 7 Feb 2017 16:41:33 +0000 Subject: Please add project Thermostat to quality outreach program In-Reply-To: References: <0f22e32a-d53b-b20c-e602-4df57cab790c@oracle.com> Message-ID: <6046705c-ba41-a489-124c-220c10825378@oracle.com> Thanks Severin, added Thermostat [1] Rgds,Rory [1] https://wiki.openjdk.java.net/display/quality/Quality+Outreach On 07/02/2017 15:29, Severin Gehwolf wrote: > Hi Rory, > > On Sun, Feb 5, 2017 at 1:33 PM, Rory O'Donnell wrote: >> Hi Severin, >> >> Nice to meet you at FOSDEM. > Likewise. > >> To list Thermostat on the wiki [1] can you provide a contact name, the >> current status of you testing against JDK 8 & JDK 9, and a CI if possible ? > You can list me as contact. We do have CI for JDK 8 which is passing, but it's > set up on a non-public instance currently. We don't do JDK 9 based CI > at this point. > > The current status of JDK 9 compatibility is that we've tried building > and running > Thermostat on JDK 9, but that has been a while ago now since we've > last tried. The next > couple of months this will be a higher priority given the JDK 9 GA timeline. > > The plan is to be JDK 9 compatible when it GAs. > > Thanks, > Severin > > >> Rgds,Rory >> >> [1] https://wiki.openjdk.java.net/display/quality/Quality+Outreach >> >> >> On 04/02/2017 17:51, Severin Gehwolf wrote: >>> Hi, >>> >>> We'd like to have Thermostat[1] added to the quality outreach program. >>> I'm one of the Thermostat developers and we've already started testing >>> Thermostat on JDK 9. >>> >>> Current status is here: >>> http://icedtea.classpath.org/bugzilla/show_bug.cgi?id=2157 >>> >>> Cheers, >>> Severin >>> >>> [1] http://icedtea.classpath.org/thermostat/ >> >> -- >> Rgds,Rory O'Donnell >> Quality Engineering Manager >> Oracle EMEA, Dublin,Ireland >> -- Rgds,Rory O'Donnell Quality Engineering Manager Oracle EMEA , Dublin, Ireland From jerboaa at gmail.com Tue Feb 7 18:00:22 2017 From: jerboaa at gmail.com (Severin Gehwolf) Date: Tue, 7 Feb 2017 19:00:22 +0100 Subject: Please add project Thermostat to quality outreach program In-Reply-To: <6046705c-ba41-a489-124c-220c10825378@oracle.com> References: <0f22e32a-d53b-b20c-e602-4df57cab790c@oracle.com> <6046705c-ba41-a489-124c-220c10825378@oracle.com> Message-ID: On Tue, Feb 7, 2017 at 5:41 PM, Rory O'Donnell wrote: > Thanks Severin, added Thermostat [1] Thanks! Could you please add the mailing list[*] too? thermostat at icedtea.classpath.org Cheers, Severin [*] http://icedtea.classpath.org/mailman/listinfo/thermostat > Rgds,Rory > > [1] https://wiki.openjdk.java.net/display/quality/Quality+Outreach > > > > On 07/02/2017 15:29, Severin Gehwolf wrote: >> >> Hi Rory, >> >> On Sun, Feb 5, 2017 at 1:33 PM, Rory O'Donnell >> wrote: >>> >>> Hi Severin, >>> >>> Nice to meet you at FOSDEM. >> >> Likewise. >> >>> To list Thermostat on the wiki [1] can you provide a contact name, the >>> current status of you testing against JDK 8 & JDK 9, and a CI if >>> possible ? >> >> You can list me as contact. We do have CI for JDK 8 which is passing, but >> it's >> set up on a non-public instance currently. We don't do JDK 9 based CI >> at this point. >> >> The current status of JDK 9 compatibility is that we've tried building >> and running >> Thermostat on JDK 9, but that has been a while ago now since we've >> last tried. The next >> couple of months this will be a higher priority given the JDK 9 GA >> timeline. >> >> The plan is to be JDK 9 compatible when it GAs. >> >> Thanks, >> Severin >> >> >>> Rgds,Rory >>> >>> [1] https://wiki.openjdk.java.net/display/quality/Quality+Outreach >>> >>> >>> On 04/02/2017 17:51, Severin Gehwolf wrote: >>>> >>>> Hi, >>>> >>>> We'd like to have Thermostat[1] added to the quality outreach program. >>>> I'm one of the Thermostat developers and we've already started testing >>>> Thermostat on JDK 9. >>>> >>>> Current status is here: >>>> http://icedtea.classpath.org/bugzilla/show_bug.cgi?id=2157 >>>> >>>> Cheers, >>>> Severin >>>> >>>> [1] http://icedtea.classpath.org/thermostat/ >>> >>> >>> -- >>> Rgds,Rory O'Donnell >>> Quality Engineering Manager >>> Oracle EMEA, Dublin,Ireland >>> > > -- > Rgds,Rory O'Donnell > Quality Engineering Manager > Oracle EMEA , Dublin, Ireland > From rory.odonnell at oracle.com Tue Feb 7 18:38:46 2017 From: rory.odonnell at oracle.com (Rory O'Donnell) Date: Tue, 7 Feb 2017 18:38:46 +0000 Subject: Please add project Thermostat to quality outreach program In-Reply-To: References: <0f22e32a-d53b-b20c-e602-4df57cab790c@oracle.com> <6046705c-ba41-a489-124c-220c10825378@oracle.com> Message-ID: <4c0a9cc5-18f2-4091-bf4a-650350109356@oracle.com> Done! On 07/02/2017 18:00, Severin Gehwolf wrote: > On Tue, Feb 7, 2017 at 5:41 PM, Rory O'Donnell wrote: >> Thanks Severin, added Thermostat [1] > Thanks! Could you please add the mailing list[*] too? > thermostat at icedtea.classpath.org > > Cheers, > Severin > > [*] http://icedtea.classpath.org/mailman/listinfo/thermostat > >> Rgds,Rory >> >> [1] https://wiki.openjdk.java.net/display/quality/Quality+Outreach >> >> >> >> On 07/02/2017 15:29, Severin Gehwolf wrote: >>> Hi Rory, >>> >>> On Sun, Feb 5, 2017 at 1:33 PM, Rory O'Donnell >>> wrote: >>>> Hi Severin, >>>> >>>> Nice to meet you at FOSDEM. >>> Likewise. >>> >>>> To list Thermostat on the wiki [1] can you provide a contact name, the >>>> current status of you testing against JDK 8 & JDK 9, and a CI if >>>> possible ? >>> You can list me as contact. We do have CI for JDK 8 which is passing, but >>> it's >>> set up on a non-public instance currently. We don't do JDK 9 based CI >>> at this point. >>> >>> The current status of JDK 9 compatibility is that we've tried building >>> and running >>> Thermostat on JDK 9, but that has been a while ago now since we've >>> last tried. The next >>> couple of months this will be a higher priority given the JDK 9 GA >>> timeline. >>> >>> The plan is to be JDK 9 compatible when it GAs. >>> >>> Thanks, >>> Severin >>> >>> >>>> Rgds,Rory >>>> >>>> [1] https://wiki.openjdk.java.net/display/quality/Quality+Outreach >>>> >>>> >>>> On 04/02/2017 17:51, Severin Gehwolf wrote: >>>>> Hi, >>>>> >>>>> We'd like to have Thermostat[1] added to the quality outreach program. >>>>> I'm one of the Thermostat developers and we've already started testing >>>>> Thermostat on JDK 9. >>>>> >>>>> Current status is here: >>>>> http://icedtea.classpath.org/bugzilla/show_bug.cgi?id=2157 >>>>> >>>>> Cheers, >>>>> Severin >>>>> >>>>> [1] http://icedtea.classpath.org/thermostat/ >>>> >>>> -- >>>> Rgds,Rory O'Donnell >>>> Quality Engineering Manager >>>> Oracle EMEA, Dublin,Ireland >>>> >> -- >> Rgds,Rory O'Donnell >> Quality Engineering Manager >> Oracle EMEA , Dublin, Ireland >> -- Rgds,Rory O'Donnell Quality Engineering Manager Oracle EMEA , Dublin, Ireland From rgolan at redhat.com Tue Feb 7 18:46:03 2017 From: rgolan at redhat.com (Roy Golan) Date: Tue, 7 Feb 2017 20:46:03 +0200 Subject: Request to add ovirt-engine to quality outreach In-Reply-To: References: Message-ID: Hi, I started testing the complication of ovirt-engine[1] using jdk9 and glad to indicate it's green. We regularly run CI jobs[2] which all run on jdk 8 and I'll work on getting one for daily jdk9. [1] ovirt.org [2] jenkins.ovirt.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From rory.odonnell at oracle.com Wed Feb 8 10:11:05 2017 From: rory.odonnell at oracle.com (Rory O'Donnell) Date: Wed, 8 Feb 2017 10:11:05 +0000 Subject: Request to add ovirt-engine to quality outreach In-Reply-To: References: Message-ID: Hi Roy, Great to hear all is working, I have added oVirt engine to wiki. Rgds,Rory On 07/02/2017 18:46, Roy Golan wrote: > Hi, > > I started testing the complication of ovirt-engine[1] using jdk9 and > glad to indicate it's green. > > We regularly run CI jobs[2] which all run on jdk 8 and I'll work on > getting one for daily jdk9. > > [1] ovirt.org > [2] jenkins.ovirt.org > > -- Rgds,Rory O'Donnell Quality Engineering Manager Oracle EMEA , Dublin, Ireland -------------- next part -------------- An HTML attachment was scrubbed... URL: From abdul.kolarkunnu at oracle.com Wed Feb 8 10:22:24 2017 From: abdul.kolarkunnu at oracle.com (Muneer Kolarkunnu) Date: Wed, 8 Feb 2017 02:22:24 -0800 (PST) Subject: JDK 9 build 155 test results now available Message-ID: <31a07f11-6d79-49d0-a79e-04c5da5e1e3c@default> JDK 9 ea build 155 test results are now available at http://www.java.net/download/openjdk/testresults/9/testresults.html The jdk test results contain 7 differences from the build 154 test results. No new testcase failures found. 0: /home/jtest/merge9/154/jdk/JTwork pass: 6,137; fail: 9; not run: 2,240 1: /home/jtest/merge9/155/jdk/JTwork pass: 6,144; fail: 6; not run: 2,243 0 1 Test fail pass com/sun/java/swing/plaf/gtk/4928019/bug4928019.java --- pass java/util/Calendar/Bug8167273.java fail pass java/util/concurrent/tck/JSR166TestCase.java fail pass java/util/concurrent/tck/JSR166TestCase.java#id1 --- pass java/util/spi/ResourceBundleControlProvider/UserDefaultControlTest.java --- pass sun/security/util/Resources/customSysClassLoader/BootMessages.java --- pass sun/security/util/Resources/customSysClassLoader/MessageFormatting.java 7 differences The hotspot test results contain 3 differences from the build 154 test results. No new testcase failures found. 0: /home/jtest/merge9/154/hotspot/JTwork pass: 1,419; fail: 7; error: 1; not run: 56 1: /home/jtest/merge9/155/hotspot/JTwork pass: 1,422; fail: 4; error: 1; not run: 56 0 1 Test fail pass gc/TestNUMAPageSize.java fail pass runtime/Thread/Fibonacci.java fail pass serviceability/threads/TestFalseDeadLock.java 3 differences The langtools test results contain 6 differences from the build 154 test results. No new testcase failures found. 0: /home/jtest/merge9/154/langtools/jtreg/JTwork pass: 3,556; not run: 301 1: /home/jtest/merge9/155/langtools/JTwork pass: 3,560; error: 1; not run: 303 0 1 Test --- pass tools/doclint/DuplicateParamTest.java --- pass tools/doclint/DuplicateReturnTest.java pass error tools/javac/failover/CheckAttributedTree.java --- pass tools/javac/processing/OverwriteInitialInput.java --- pass tools/javap/typeAnnotations/AnnotationDefaultNewlineTest.java --- pass tools/javap/typeAnnotations/InvisibleParameterAnnotationsTest.java 6 differences The nashorn test result is available at http://download.java.net/openjdk/testresults/9/archives/155/emailable-report.html -- Regards, Abdul Muneer Quality Engineer Oracle, Bangalore, India -------------- next part -------------- An HTML attachment was scrubbed... URL: From rgolan at redhat.com Wed Feb 8 12:32:23 2017 From: rgolan at redhat.com (Roy Golan) Date: Wed, 8 Feb 2017 14:32:23 +0200 Subject: Request to add ovirt-engine to quality outreach In-Reply-To: References: Message-ID: On 8 February 2017 at 12:11, Rory O'Donnell wrote: > Hi Roy, > > Great to hear all is working, I have added oVirt engine to wiki. > > Rgds,Rory > > Thanks. Our issues link is https://bugzilla.redhat.com/enter_bug.cgi?product=ovirt-engine > On 07/02/2017 18:46, Roy Golan wrote: > > Hi, > > I started testing the complication of ovirt-engine[1] using jdk9 and glad > to indicate it's green. > > We regularly run CI jobs[2] which all run on jdk 8 and I'll work on > getting one for daily jdk9. > > [1] ovirt.org > [2] jenkins.ovirt.org > > > > -- > Rgds,Rory O'Donnell > Quality Engineering Manager > Oracle EMEA , Dublin, Ireland > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From rory.odonnell at oracle.com Wed Feb 8 15:27:24 2017 From: rory.odonnell at oracle.com (Rory O'Donnell) Date: Wed, 8 Feb 2017 15:27:24 +0000 Subject: Request to add ovirt-engine to quality outreach In-Reply-To: References: Message-ID: <1d94339d-fcda-4239-f768-69315ed883e4@oracle.com> Done! Rgds,Rory On 08/02/2017 12:32, Roy Golan wrote: > > > On 8 February 2017 at 12:11, Rory O'Donnell > wrote: > > Hi Roy, > > Great to hear all is working, I have added oVirt engine to wiki. > > Rgds,Rory > > > > Thanks. Our issues link is > https://bugzilla.redhat.com/enter_bug.cgi?product=ovirt-engine > > > On 07/02/2017 18:46, Roy Golan wrote: >> Hi, >> >> I started testing the complication of ovirt-engine[1] using jdk9 >> and glad to indicate it's green. >> >> We regularly run CI jobs[2] which all run on jdk 8 and I'll work >> on getting one for daily jdk9. >> >> [1] ovirt.org >> [2] jenkins.ovirt.org >> >> > > -- > Rgds,Rory O'Donnell > Quality Engineering Manager > Oracle EMEA , Dublin, Ireland > > -- Rgds,Rory O'Donnell Quality Engineering Manager Oracle EMEA , Dublin, Ireland -------------- next part -------------- An HTML attachment was scrubbed... URL: From abdul.kolarkunnu at oracle.com Fri Feb 10 11:44:57 2017 From: abdul.kolarkunnu at oracle.com (Muneer Kolarkunnu) Date: Fri, 10 Feb 2017 03:44:57 -0800 (PST) Subject: JDK 9 build 156 test results now available Message-ID: JDK 9 ea build 156 test results are now available at http://www.java.net/download/openjdk/testresults/9/testresults.html The jdk test results contain 13 differences from the build 155 test results. There is 1 testcase failure, this failure is under investigation. 0: /home/jtest/merge9/155/jdk/JTwork pass: 6,144; fail: 6; not run: 2,243 1: /home/jtest/merge9/156/jdk/JTwork pass: 6,150; fail: 7; error: 1; not run: 2,245 0 1 Test --- pass com/sun/management/DiagnosticCommandMBean/DcmdMBeanPermissionsTest.java --- pass java/net/ProxySelector/SystemProxies.java --- pass java/util/concurrent/ConcurrentLinkedQueue/WhiteBox.java --- pass java/util/concurrent/LinkedTransferQueue/WhiteBox.java --- pass javax/imageio/plugins/tiff/TIFFCreateArrayForTypeTest.java pass --- sun/management/AgentCMETest.java pass --- sun/management/AgentCheckTest.java --- fail sun/management/jdp/JdpJmxRemoteDynamicPortTest.java --- pass sun/security/pkcs12/MixedcaseAlias.java pass error sun/tools/jstatd/TestJstatdExternalRegistry.java --- pass tools/launcher/LauncherMessageTest.java --- pass tools/schemagen/MultiReleaseJarTest.java --- pass tools/wsgen/MultiReleaseJarTest.java 13 differences The hotspot test results contain 26 differences from the build 155 test results. There are 6 testcase failures, these failures are under investigation. 0: /home/jtest/merge9/155/hotspot/JTwork pass: 1,422; fail: 4; error: 1; not run: 56 1: /home/jtest/merge9/156/hotspot/JTwork pass: 1,421; fail: 6; not run: 59 0 1 Test pass --- compiler/aot/cli/jaotc/ClasspathOptionTest.java pass --- compiler/aot/fingerprint/SelfChanged.java pass --- compiler/aot/fingerprint/SelfChangedCDS.java pass --- compiler/aot/fingerprint/SuperChanged.java --- pass compiler/arraycopy/TestArrayCopyUNCBadMem.java --- pass compiler/c1/Test8172751.java pass --- compiler/c2/cr7200264/TestIntVect.java --- pass compiler/gcbarriers/TestMembarDependencies.java pass --- compiler/jvmci/compilerToVM/CanInlineMethodTest.java --- pass compiler/jvmci/compilerToVM/HasNeverInlineDirectiveTest.java --- pass compiler/jvmci/compilerToVM/IsCompilableTest.java fail --- compiler/loopopts/UseCountedLoopSafepointsTest.java pass --- gc/g1/logging/TestG1LoggingFailure.java --- pass gc/stress/TestStressG1Humongous.java fail pass gc/stress/gcbasher/TestGCBasherWithCMS.java fail pass gc/stress/gcbasher/TestGCBasherWithG1.java fail pass gc/stress/gcbasher/TestGCBasherWithSerial.java pass fail runtime/ClassFile/FormatCheckingTest.java pass fail runtime/EnclosingMethodAttr/EnclMethodAttr.java pass fail runtime/classFileParserBug/ClassFileParserBug.java pass fail runtime/duplAttributes/DuplAttributesTest.java --- pass runtime/modules/AccessCheck/AccessExportTwice.java --- pass runtime/modules/AccessCheck/AccessReadTwice.java pass fail runtime/verifier/OverriderMsg.java pass fail runtime/verifier/TestANewArray.java error pass serviceability/sa/jmap-hprof/JMapHProfLargeHeapTest.java 26 differences The langtools test results contain 0 differences from the build 155 test results. The nashorn test result is available at http://download.java.net/openjdk/testresults/9/archives/156/emailable-report.html -- Regards, Abdul Muneer Quality Engineer Oracle, Bangalore, India -------------- next part -------------- An HTML attachment was scrubbed... URL: From ceki at qos.ch Tue Feb 14 10:10:48 2017 From: ceki at qos.ch (=?UTF-8?B?Q2VraSBHw7xsY8O8?=) Date: Tue, 14 Feb 2017 11:10:48 +0100 Subject: Started testing Java9 with log4j 1.2, SLF4J and logback projects Message-ID: <6729acce-2489-7b9c-3a32-770492799db3@qos.ch> Hi All, We started testing SLF4J and logback projects using Java 9, more specifically build 154. As such, I would appreciate if you could add the following details onto the Quality Outreach wiki page. Contact: Ceki G?lc? SLF4J mailing list slf4j-dev AT qos DOT ch Logback mailing list logback-dev AT qos DOT ch Initial testing results ======================= Initial testing indicates that log4j version 1.2.x is unable to parse the result of the call System.getProperties("java.version"). The returned string is "9-ea". However, log4j 1.2.x expects a string in the form "1\.*", for example "1.6", "1.7" etc. If the string is not in the correct form, log4j 1.2.x conservatively assumes that it is running under Java 1.1 and disables certain important functions, such as MDC support. The code in question is the static initializer of the org.apache.log4j.helpers.Loader class. Log4j 1.2.x is no longer maintained. However, there are innumerably many projects which still use log4j 1.2.x. I would suggest that the string returned be in the form "1\.9*" such as "1.9EA" so as not to break log4j 1.2.x under Java 9. Many thanks in advance for taking the above into consideration. Best regards, -- Ceki G?lc? From rory.odonnell at oracle.com Tue Feb 14 10:26:37 2017 From: rory.odonnell at oracle.com (Rory O'Donnell) Date: Tue, 14 Feb 2017 10:26:37 +0000 Subject: Started testing Java9 with log4j 1.2, SLF4J and logback projects In-Reply-To: <6729acce-2489-7b9c-3a32-770492799db3@qos.ch> References: <6729acce-2489-7b9c-3a32-770492799db3@qos.ch> Message-ID: <61d6a570-82a2-a456-d3e5-706edbe8c5e3@oracle.com> Hi Ceki, Can you read JEP 223 it describes how the new version string is implemented in JDK 9. Is logback working with JDK 9 ? Rgds,Rory On 14/02/2017 10:10, Ceki G?lc? wrote: > > Hi All, > > > We started testing SLF4J and logback projects using Java 9, more > specifically build 154. As such, I would appreciate if you could add > the following details onto the Quality Outreach wiki page. > > Contact: Ceki G?lc? > SLF4J mailing list slf4j-dev AT qos DOT ch > Logback mailing list logback-dev AT qos DOT ch > > Initial testing results > ======================= > > Initial testing indicates that log4j version 1.2.x is unable to parse > the result of the call System.getProperties("java.version"). The > returned string is "9-ea". However, log4j 1.2.x expects a string in > the form "1\.*", for example "1.6", "1.7" etc. > > If the string is not in the correct form, log4j 1.2.x conservatively > assumes that it is running under Java 1.1 and disables certain > important functions, such as MDC support. The code in question is the > static initializer of the org.apache.log4j.helpers.Loader class. > > Log4j 1.2.x is no longer maintained. However, there are innumerably > many projects which still use log4j 1.2.x. > > I would suggest that the string returned be in the form "1\.9*" such as > "1.9EA" so as not to break log4j 1.2.x under Java 9. > > Many thanks in advance for taking the above into consideration. > > Best regards, > > -- > Ceki G?lc? > > > -- Rgds,Rory O'Donnell Quality Engineering Manager Oracle EMEA , Dublin, Ireland -------------- next part -------------- An HTML attachment was scrubbed... URL: From ceki at qos.ch Tue Feb 14 11:14:30 2017 From: ceki at qos.ch (=?UTF-8?B?Q2VraSBHw7xsY8O8?=) Date: Tue, 14 Feb 2017 12:14:30 +0100 Subject: Started testing Java9 with log4j 1.2, SLF4J and logback projects In-Reply-To: <61d6a570-82a2-a456-d3e5-706edbe8c5e3@oracle.com> References: <6729acce-2489-7b9c-3a32-770492799db3@qos.ch> <61d6a570-82a2-a456-d3e5-706edbe8c5e3@oracle.com> Message-ID: <254c8937-8d95-3281-587a-70cf2a4f57c1@qos.ch> Hi Rory, Thank you for the pointer to JEP 223. Logback would also fail to parse the new java.version property. I created issue LOGBACK-1260 (See [1]) to track this problem which I expect will be fixed in version 1.2.2, that is the next release of logback. In the context of SLF4J, the build of the slf4j-log4j12 module fails since log4j can no longer correctly detect the version of Java and shuts down MDC support. In short, the changes introduced in JEP 223 have significant consequences for log4j 1.2.x and by ricochet for SLF4J. Best regards, -- Ceki G?lc? [1] https://jira.qos.ch/browse/LOGBACK-1260 On 2/14/2017 11:26, Rory O'Donnell wrote: > Hi Ceki, > > Can you read JEP 223 it describes > how the new version string is implemented in JDK 9. > > Is logback working with JDK 9 ? > > Rgds,Rory > > On 14/02/2017 10:10, Ceki G?lc? wrote: >> >> Hi All, >> >> >> We started testing SLF4J and logback projects using Java 9, more >> specifically build 154. As such, I would appreciate if you could add >> the following details onto the Quality Outreach wiki page. >> >> Contact: Ceki G?lc? >> SLF4J mailing list slf4j-dev AT qos DOT ch >> Logback mailing list logback-dev AT qos DOT ch >> >> Initial testing results >> ======================= >> >> Initial testing indicates that log4j version 1.2.x is unable to parse >> the result of the call System.getProperties("java.version"). The >> returned string is "9-ea". However, log4j 1.2.x expects a string in >> the form "1\.*", for example "1.6", "1.7" etc. >> >> If the string is not in the correct form, log4j 1.2.x conservatively >> assumes that it is running under Java 1.1 and disables certain >> important functions, such as MDC support. The code in question is the >> static initializer of the org.apache.log4j.helpers.Loader class. >> >> Log4j 1.2.x is no longer maintained. However, there are innumerably >> many projects which still use log4j 1.2.x. >> >> I would suggest that the string returned be in the form "1\.9*" such as >> "1.9EA" so as not to break log4j 1.2.x under Java 9. >> >> Many thanks in advance for taking the above into consideration. >> >> Best regards, >> >> -- >> Ceki G?lc? >> >> >> > > -- > Rgds,Rory O'Donnell > Quality Engineering Manager > Oracle EMEA , Dublin, Ireland > From rory.odonnell at oracle.com Tue Feb 14 12:54:34 2017 From: rory.odonnell at oracle.com (Rory O'Donnell) Date: Tue, 14 Feb 2017 12:54:34 +0000 Subject: Started testing Java9 with log4j 1.2, SLF4J and logback projects In-Reply-To: <254c8937-8d95-3281-587a-70cf2a4f57c1@qos.ch> References: <6729acce-2489-7b9c-3a32-770492799db3@qos.ch> <61d6a570-82a2-a456-d3e5-706edbe8c5e3@oracle.com> <254c8937-8d95-3281-587a-70cf2a4f57c1@qos.ch> Message-ID: Hi Ceki, I have updated the wiki. Rgds,Rory On 14/02/2017 11:14, Ceki G?lc? wrote: > Hi Rory, > > Thank you for the pointer to JEP 223. > > Logback would also fail to parse the new java.version property. I > created issue LOGBACK-1260 (See [1]) to track this problem which I > expect will be fixed in version 1.2.2, that is the next release of > logback. > > In the context of SLF4J, the build of the slf4j-log4j12 module fails > since log4j can no longer correctly detect the version of Java and > shuts down MDC support. In short, the changes introduced in JEP 223 > have significant consequences for log4j 1.2.x and by ricochet for SLF4J. > > Best regards, > > -- > Ceki G?lc? > > [1] https://jira.qos.ch/browse/LOGBACK-1260 > > On 2/14/2017 11:26, Rory O'Donnell wrote: >> Hi Ceki, >> >> Can you read JEP 223 it describes >> how the new version string is implemented in JDK 9. >> >> Is logback working with JDK 9 ? >> >> Rgds,Rory >> >> On 14/02/2017 10:10, Ceki G?lc? wrote: >>> >>> Hi All, >>> >>> >>> We started testing SLF4J and logback projects using Java 9, more >>> specifically build 154. As such, I would appreciate if you could add >>> the following details onto the Quality Outreach wiki page. >>> >>> Contact: Ceki G?lc? >>> SLF4J mailing list slf4j-dev AT qos DOT ch >>> Logback mailing list logback-dev AT qos DOT ch >>> >>> Initial testing results >>> ======================= >>> >>> Initial testing indicates that log4j version 1.2.x is unable to parse >>> the result of the call System.getProperties("java.version"). The >>> returned string is "9-ea". However, log4j 1.2.x expects a string in >>> the form "1\.*", for example "1.6", "1.7" etc. >>> >>> If the string is not in the correct form, log4j 1.2.x conservatively >>> assumes that it is running under Java 1.1 and disables certain >>> important functions, such as MDC support. The code in question is the >>> static initializer of the org.apache.log4j.helpers.Loader class. >>> >>> Log4j 1.2.x is no longer maintained. However, there are innumerably >>> many projects which still use log4j 1.2.x. >>> >>> I would suggest that the string returned be in the form "1\.9*" such as >>> "1.9EA" so as not to break log4j 1.2.x under Java 9. >>> >>> Many thanks in advance for taking the above into consideration. >>> >>> Best regards, >>> >>> -- >>> Ceki G?lc? >>> >>> >>> >> >> -- >> Rgds,Rory O'Donnell >> Quality Engineering Manager >> Oracle EMEA , Dublin, Ireland >> -- Rgds,Rory O'Donnell Quality Engineering Manager Oracle EMEA , Dublin, Ireland From dalibor.topic at oracle.com Tue Feb 14 16:42:01 2017 From: dalibor.topic at oracle.com (dalibor topic) Date: Tue, 14 Feb 2017 17:42:01 +0100 Subject: Started testing Java9 with log4j 1.2, SLF4J and logback projects In-Reply-To: <254c8937-8d95-3281-587a-70cf2a4f57c1@qos.ch> References: <6729acce-2489-7b9c-3a32-770492799db3@qos.ch> <61d6a570-82a2-a456-d3e5-706edbe8c5e3@oracle.com> <254c8937-8d95-3281-587a-70cf2a4f57c1@qos.ch> Message-ID: <373a89a5-67f4-1db4-8a33-875e5e4d88c7@oracle.com> On 14.02.2017 12:14, Ceki G?lc? wrote: > In the context of SLF4J, the build of the slf4j-log4j12 module fails > since log4j can no longer correctly detect the version of Java and shuts > down MDC support. In short, the changes introduced in JEP 223 have > significant consequences for log4j 1.2.x and by ricochet for SLF4J. Hi Ceki, general information about Log4J 1.x on JDK9 can be found at https://blogs.apache.org/logging/entry/moving_on_to_log4j_2 . In particular, the blog points to a potential workaround for Log4j 1.x, although, of course, migrating off libraries that are no longer maintained should be the preferred choice for most developers. cheers, dalibor topic -- Dalibor Topic | Principal Product Manager Phone: +494089091214 | Mobile: +491737185961 ORACLE Deutschland B.V. & Co. KG | K?hneh?fe 5 | 22761 Hamburg ORACLE Deutschland B.V. & Co. KG Hauptverwaltung: Riesstr. 25, D-80992 M?nchen Registergericht: Amtsgericht M?nchen, HRA 95603 Komplement?rin: ORACLE Deutschland Verwaltung B.V. Hertogswetering 163/167, 3543 AS Utrecht, Niederlande Handelsregister der Handelskammer Midden-Niederlande, Nr. 30143697 Gesch?ftsf?hrer: Alexander van der Ven, Jan Schultheiss, Val Maher Oracle is committed to developing practices and products that help protect the environment From ceki at qos.ch Tue Feb 14 21:57:44 2017 From: ceki at qos.ch (=?UTF-8?B?Q2VraSBHw7xsY8O8?=) Date: Tue, 14 Feb 2017 22:57:44 +0100 Subject: Started testing Java9 with log4j 1.2, SLF4J and logback projects In-Reply-To: <373a89a5-67f4-1db4-8a33-875e5e4d88c7@oracle.com> References: <6729acce-2489-7b9c-3a32-770492799db3@qos.ch> <61d6a570-82a2-a456-d3e5-706edbe8c5e3@oracle.com> <254c8937-8d95-3281-587a-70cf2a4f57c1@qos.ch> <373a89a5-67f4-1db4-8a33-875e5e4d88c7@oracle.com> Message-ID: <84976826-6971-e924-677d-e9e48423cf5b@qos.ch> Hi Dalibor, Thank you for the useful pointer to a possible workaround. The issue impacting the slf4j-log4j12 module (which relies on log4j 1.2.17) is now fixed. The fix will ship with release 1.7.23 of SLF4J. See also https://jira.qos.ch/browse/SLF4J-393 -- Ceki On 2/14/2017 17:42, dalibor topic wrote: > > > On 14.02.2017 12:14, Ceki G?lc? wrote: >> In the context of SLF4J, the build of the slf4j-log4j12 module fails >> since log4j can no longer correctly detect the version of Java and shuts >> down MDC support. In short, the changes introduced in JEP 223 have >> significant consequences for log4j 1.2.x and by ricochet for SLF4J. > > Hi Ceki, > > general information about Log4J 1.x on JDK9 can be found at > https://blogs.apache.org/logging/entry/moving_on_to_log4j_2 . > > In particular, the blog points to a potential workaround for Log4j 1.x, > although, of course, migrating off libraries that are no longer > maintained should be the preferred choice for most developers. > > cheers, > dalibor topic > From dalibor.topic at oracle.com Wed Feb 15 10:00:36 2017 From: dalibor.topic at oracle.com (dalibor topic) Date: Wed, 15 Feb 2017 11:00:36 +0100 Subject: Started testing Java9 with log4j 1.2, SLF4J and logback projects In-Reply-To: <84976826-6971-e924-677d-e9e48423cf5b@qos.ch> References: <6729acce-2489-7b9c-3a32-770492799db3@qos.ch> <61d6a570-82a2-a456-d3e5-706edbe8c5e3@oracle.com> <254c8937-8d95-3281-587a-70cf2a4f57c1@qos.ch> <373a89a5-67f4-1db4-8a33-875e5e4d88c7@oracle.com> <84976826-6971-e924-677d-e9e48423cf5b@qos.ch> Message-ID: <96be93ac-b79a-6999-ef0a-e155b30ed71f@oracle.com> On 14.02.2017 22:57, Ceki G?lc? wrote: > > Hi Dalibor, > > Thank you for the useful pointer to a possible workaround. > > The issue impacting the slf4j-log4j12 module (which relies on log4j > 1.2.17) is now fixed. The fix will ship with release 1.7.23 of SLF4J. > > See also https://jira.qos.ch/browse/SLF4J-393 Thanks, Ceki - great to hear you could make the concept in the workaround proposed in the Log4j 1.x EOL blog work for your use case as well. cheers, dalibor topic -- Dalibor Topic | Principal Product Manager Phone: +494089091214 | Mobile: +491737185961 ORACLE Deutschland B.V. & Co. KG | K?hneh?fe 5 | 22761 Hamburg ORACLE Deutschland B.V. & Co. KG Hauptverwaltung: Riesstr. 25, D-80992 M?nchen Registergericht: Amtsgericht M?nchen, HRA 95603 Komplement?rin: ORACLE Deutschland Verwaltung B.V. Hertogswetering 163/167, 3543 AS Utrecht, Niederlande Handelsregister der Handelskammer Midden-Niederlande, Nr. 30143697 Gesch?ftsf?hrer: Alexander van der Ven, Jan Schultheiss, Val Maher Oracle is committed to developing practices and products that help protect the environment From reto.merz at abacus.ch Fri Feb 24 10:10:18 2017 From: reto.merz at abacus.ch (Reto Merz) Date: Fri, 24 Feb 2017 11:10:18 +0100 Subject: jdk-9-ea+157_windows-x64_bin.exe is reported as virus/malware by Firefox and Chrome Message-ID: <7ac874a4-851a-4697-8784-418eff36c5c1@abacus.ch> Hello, Up-to-date Firefox and Chrome browser are reporting that http://download.java.net/java/jdk9/archive/157/binaries/jdk-9-ea+157_windows-x64_bin.exe includes a virus or malware. So the download is blocked by default. Regards Reto From nhoj.patrick at gmail.com Fri Feb 24 10:26:16 2017 From: nhoj.patrick at gmail.com (John Patrick) Date: Fri, 24 Feb 2017 10:26:16 +0000 Subject: jdk-9-ea+157_windows-x64_bin.exe is reported as virus/malware by Firefox and Chrome In-Reply-To: <7ac874a4-851a-4697-8784-418eff36c5c1@abacus.ch> References: <7ac874a4-851a-4697-8784-418eff36c5c1@abacus.ch> Message-ID: I've just tried and they downloading fine for me, latest versions of both Firefox and Chrome but I'm on a Mac. What anti virus program are you using and is it up to date, and also what operating system are you downloading them on? John On 24 February 2017 at 10:10, Reto Merz wrote: > Hello, > > Up-to-date Firefox and Chrome browser are reporting that > http://download.java.net/java/jdk9/archive/157/binaries/jdk-9-ea+157_windows-x64_bin.exe > includes a virus or malware. So the download is blocked by default. > > Regards > Reto > > From reto.merz at abacus.ch Fri Feb 24 10:31:16 2017 From: reto.merz at abacus.ch (Reto Merz) Date: Fri, 24 Feb 2017 11:31:16 +0100 Subject: jdk-9-ea+157_windows-x64_bin.exe is reported as virus/malware by Firefox and Chrome Message-ID: I use Windows 2012 R2 with latest windows update ; no virus scanner installed: C:\Windows\System32>ver Microsoft Windows [Version 6.3.9600] Firefox Version 51.0.1 (32-bit) Chrome Version 56.0.2924.87 Reto > On 24 February 2017 at 11:26, John Patrick wrote: > I've just tried and they downloading fine for me, latest versions of > both Firefox and Chrome but I'm on a Mac. > > What anti virus program are you using and is it up to date, and also > what operating system are you downloading them on? > > John > > > On 24 February 2017 at 10:10, Reto Merz wrote: > > Hello, > > > > Up-to-date Firefox and Chrome browser are reporting that > > http://download.java.net/java/jdk9/archive/157/binaries/jdk-9- > ea+157_windows-x64_bin.exe > > includes a virus or malware. So the download is blocked by default. > > > > Regards > > Reto > > > > From dalibor.topic at oracle.com Fri Feb 24 21:45:28 2017 From: dalibor.topic at oracle.com (dalibor topic) Date: Fri, 24 Feb 2017 22:45:28 +0100 Subject: jdk-9-ea+157_windows-x64_bin.exe is reported as virus/malware by Firefox and Chrome In-Reply-To: References: Message-ID: <7c9f8681-7ff5-1d97-49a1-1d784dbe4e04@oracle.com> Hi Reto, Thanks for reporting the issue. We're looking into it and will let you know when it's fixed. cheers, dalibor topic On 24.02.2017 11:31, Reto Merz wrote: > I use Windows 2012 R2 with latest windows update ; no virus scanner installed: > > C:\Windows\System32>ver > Microsoft Windows [Version 6.3.9600] > > Firefox Version 51.0.1 (32-bit) > Chrome Version 56.0.2924.87 > > Reto > > >> On 24 February 2017 at 11:26, John Patrick wrote: >> I've just tried and they downloading fine for me, latest versions of >> both Firefox and Chrome but I'm on a Mac. >> >> What anti virus program are you using and is it up to date, and also >> what operating system are you downloading them on? >> >> John >> >> >> On 24 February 2017 at 10:10, Reto Merz wrote: >>> Hello, >>> >>> Up-to-date Firefox and Chrome browser are reporting that >>> http://download.java.net/java/jdk9/archive/157/binaries/jdk-9- >> ea+157_windows-x64_bin.exe >>> includes a virus or malware. So the download is blocked by default. >>> >>> Regards >>> Reto >>> >>> > -- Dalibor Topic | Principal Product Manager Phone: +494089091214 | Mobile: +491737185961 ORACLE Deutschland B.V. & Co. KG | K?hneh?fe 5 | 22761 Hamburg ORACLE Deutschland B.V. & Co. KG Hauptverwaltung: Riesstr. 25, D-80992 M?nchen Registergericht: Amtsgericht M?nchen, HRA 95603 Komplement?rin: ORACLE Deutschland Verwaltung B.V. Hertogswetering 163/167, 3543 AS Utrecht, Niederlande Handelsregister der Handelskammer Midden-Niederlande, Nr. 30143697 Gesch?ftsf?hrer: Alexander van der Ven, Jan Schultheiss, Val Maher Oracle is committed to developing practices and products that help protect the environment From rory.odonnell at oracle.com Tue Feb 28 10:40:42 2017 From: rory.odonnell at oracle.com (Rory O'Donnell) Date: Tue, 28 Feb 2017 10:40:42 +0000 Subject: jdk-9-ea+157_windows-x64_bin.exe is reported as virus/malware by Firefox and Chrome In-Reply-To: References: Message-ID: Hi Reto, Thanks for logging this issue, it appears b158 also suffers from the same problem. Will let you know as soon as this is fixed. Rgds,Rory On 24/02/2017 10:31, Reto Merz wrote: > I use Windows 2012 R2 with latest windows update ; no virus scanner installed: > > C:\Windows\System32>ver > Microsoft Windows [Version 6.3.9600] > > Firefox Version 51.0.1 (32-bit) > Chrome Version 56.0.2924.87 > > Reto > > >> On 24 February 2017 at 11:26, John Patrick wrote: >> I've just tried and they downloading fine for me, latest versions of >> both Firefox and Chrome but I'm on a Mac. >> >> What anti virus program are you using and is it up to date, and also >> what operating system are you downloading them on? >> >> John >> >> >> On 24 February 2017 at 10:10, Reto Merz wrote: >>> Hello, >>> >>> Up-to-date Firefox and Chrome browser are reporting that >>> http://download.java.net/java/jdk9/archive/157/binaries/jdk-9- >> ea+157_windows-x64_bin.exe >>> includes a virus or malware. So the download is blocked by default. >>> >>> Regards >>> Reto >>> >>> -- Rgds,Rory O'Donnell Quality Engineering Manager Oracle EMEA, Dublin,Ireland