From vincent.privat at gmail.com Fri Oct 2 20:58:10 2015 From: vincent.privat at gmail.com (Vincent Privat) Date: Fri, 2 Oct 2015 22:58:10 +0200 Subject: Quality outreach: JOSM and OpenJDK adoption In-Reply-To: <56098A62.1040601@oracle.com> References: <56098A62.1040601@oracle.com> Message-ID: Hi everyone, Thanks for the welcoming feedback! You can mention me as contact on the wiki page, and josm-dev as mailing list. I am interested in receiving e-mails for new EA builds. We're going to give a try to Jigsaw builds, too. Is there now something special to do when we report bugs? (like specific keywords or something) Regards, Vincent 2015-09-28 20:43 GMT+02:00 Jonathan Gibbons : > I tried your query [6], but that catches resolved issues as well as > unresolved ones. > > I found only 5 open issues containing "JOSM". > > > https://bugs.openjdk.java.net/browse/JDK-8087915?jql=project%20%3D%20jdk%20and%20resolution%20is%20empty%20and%20text%20~%20josm > > -- Jon > > > > On 09/27/2015 06:03 AM, Martijn Verburg wrote: > > Hi Vincent, > > I'd say that would be most welcome - Rory? > > On Sunday, 27 September 2015, Vincent Privat > wrote: > >> Hi, >> I am a core developer of JOSM, the Java OpenStreetMap Editor. If you don't >> know about it, it is an extensible editor for OpenStreetMap (OSM), written >> in Java 7, under GPL license. You can find more information about it on >> [1], [2] and [3]. >> >> The first version of JOSM was released 10 years ago, in 2005. At this time >> it was compatible with Java 5. We have since switched to Java 6, then 7. >> We >> are now currently considering the migration to Java 8 [4] and began to >> actively test JOSM with early builds of Java 9 [5]. The current test >> results with Java 9 are excellent as all unit tests are OK. >> >> During the past years the JOSM community has submitted several bug reports >> to Sun/Oracle on the public bug tracker. I don't have the exhaustive list, >> but 11 recent tickets can be found by searching "JOSM" keyword on JBS [6]. >> >> Given this status, I wonder if JOSM can be mentioned in the Quality >> Outreach [7], and if some of our bug reports may be considered as valuable >> in the Quality Outreach report [8]. >> >> Best regards, >> Vincent, for the JOSM team >> >> [1] https://josm.openstreetmap.de/ >> [2] http://wiki.openstreetmap.org/wiki/JOSM >> [3] https://en.wikipedia.org/wiki/JOSM >> [4] https://josm.openstreetmap.de/ticket/11390 >> [5] https://josm.openstreetmap.de/jenkins/job/JOSM/ >> [6] >> >> https://bugs.openjdk.java.net/sr/jira.issueviews:searchrequest-printable/temp/SearchRequest.html?jqlQuery=text+~+%22josm%22 >> >> [7] https://wiki.openjdk.java.net/display/quality/Quality+Outreach >> [8] >> >> https://wiki.openjdk.java.net/display/quality/Quality+Outreach+report+Sept+%272015 >> > > > -- > Cheers, Martijn (Sent from Gmail Mobile) > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From rory.odonnell at oracle.com Mon Oct 5 08:31:54 2015 From: rory.odonnell at oracle.com (Rory O'Donnell) Date: Mon, 5 Oct 2015 09:31:54 +0100 Subject: Quality outreach: JOSM and OpenJDK adoption In-Reply-To: References: <56098A62.1040601@oracle.com> Message-ID: <5612357A.70406@oracle.com> On 02/10/2015 21:58, Vincent Privat wrote: > Hi everyone, > Thanks for the welcoming feedback! > You can mention me as contact on the wiki page, and josm-dev as > mailing list. Done. Do you have a CI link that I can point to ? > I am interested in receiving e-mails for new EA builds. We're going to > give a try to Jigsaw builds, too. I will add you to the list. > Is there now something special to do when we report bugs? (like > specific keywords or something) I suggest you send all feedback to the jigsaw-dev mailing list too. Rgds,Rory > Regards, > Vincent > > 2015-09-28 20:43 GMT+02:00 Jonathan Gibbons > >: > > I tried your query [6], but that catches resolved issues as well > as unresolved ones. > > I found only 5 open issues containing "JOSM". > > https://bugs.openjdk.java.net/browse/JDK-8087915?jql=project%20%3D%20jdk%20and%20resolution%20is%20empty%20and%20text%20~%20josm > > > -- Jon > > > > On 09/27/2015 06:03 AM, Martijn Verburg wrote: >> Hi Vincent, >> >> I'd say that would be most welcome - Rory? >> >> On Sunday, 27 September 2015, Vincent Privat >> > wrote: >> >> Hi, >> I am a core developer of JOSM, the Java OpenStreetMap Editor. >> If you don't >> know about it, it is an extensible editor for OpenStreetMap >> (OSM), written >> in Java 7, under GPL license. You can find more information >> about it on >> [1], [2] and [3]. >> >> The first version of JOSM was released 10 years ago, in 2005. >> At this time >> it was compatible with Java 5. We have since switched to Java >> 6, then 7. We >> are now currently considering the migration to Java 8 [4] and >> began to >> actively test JOSM with early builds of Java 9 [5]. The >> current test >> results with Java 9 are excellent as all unit tests are OK. >> >> During the past years the JOSM community has submitted >> several bug reports >> to Sun/Oracle on the public bug tracker. I don't have the >> exhaustive list, >> but 11 recent tickets can be found by searching "JOSM" >> keyword on JBS [6]. >> >> Given this status, I wonder if JOSM can be mentioned in the >> Quality >> Outreach [7], and if some of our bug reports may be >> considered as valuable >> in the Quality Outreach report [8]. >> >> Best regards, >> Vincent, for the JOSM team >> >> [1] https://josm.openstreetmap.de/ >> [2] http://wiki.openstreetmap.org/wiki/JOSM >> [3] https://en.wikipedia.org/wiki/JOSM >> [4] https://josm.openstreetmap.de/ticket/11390 >> [5] https://josm.openstreetmap.de/jenkins/job/JOSM/ >> [6] >> https://bugs.openjdk.java.net/sr/jira.issueviews:searchrequest-printable/temp/SearchRequest.html?jqlQuery=text+~+%22josm%22 >> >> [7] >> https://wiki.openjdk.java.net/display/quality/Quality+Outreach >> [8] >> https://wiki.openjdk.java.net/display/quality/Quality+Outreach+report+Sept+%272015 >> >> >> >> -- >> Cheers, Martijn (Sent from Gmail Mobile) > > -- Rgds,Rory O'Donnell Quality Engineering Manager Oracle EMEA , Dublin, Ireland -------------- next part -------------- An HTML attachment was scrubbed... URL: From vincent.privat at gmail.com Mon Oct 5 20:50:45 2015 From: vincent.privat at gmail.com (Vincent Privat) Date: Mon, 5 Oct 2015 22:50:45 +0200 Subject: Quality outreach: JOSM and OpenJDK adoption In-Reply-To: <5612357A.70406@oracle.com> References: <56098A62.1040601@oracle.com> <5612357A.70406@oracle.com> Message-ID: Thanks! You can add this link as CI: https://josm.openstreetmap.de/jenkins/ Best regards, Vincent 2015-10-05 10:31 GMT+02:00 Rory O'Donnell : > > > On 02/10/2015 21:58, Vincent Privat wrote: > > Hi everyone, > Thanks for the welcoming feedback! > You can mention me as contact on the wiki page, and josm-dev as mailing > list. > > Done. > > Do you have a CI link that I can point to ? > > I am interested in receiving e-mails for new EA builds. We're going to > give a try to Jigsaw builds, too. > > I will add you to the list. > > Is there now something special to do when we report bugs? (like specific > keywords or something) > > I suggest you send all feedback to the jigsaw-dev mailing list too. > > Rgds,Rory > > Regards, > Vincent > > 2015-09-28 20:43 GMT+02:00 Jonathan Gibbons : > >> I tried your query [6], but that catches resolved issues as well as >> unresolved ones. >> >> I found only 5 open issues containing "JOSM". >> >> >> https://bugs.openjdk.java.net/browse/JDK-8087915?jql=project%20%3D%20jdk%20and%20resolution%20is%20empty%20and%20text%20~%20josm >> >> >> -- Jon >> >> >> >> On 09/27/2015 06:03 AM, Martijn Verburg wrote: >> >> Hi Vincent, >> >> I'd say that would be most welcome - Rory? >> >> On Sunday, 27 September 2015, Vincent Privat < >> vincent.privat at gmail.com> wrote: >> >>> Hi, >>> I am a core developer of JOSM, the Java OpenStreetMap Editor. If you >>> don't >>> know about it, it is an extensible editor for OpenStreetMap (OSM), >>> written >>> in Java 7, under GPL license. You can find more information about it on >>> [1], [2] and [3]. >>> >>> The first version of JOSM was released 10 years ago, in 2005. At this >>> time >>> it was compatible with Java 5. We have since switched to Java 6, then 7. >>> We >>> are now currently considering the migration to Java 8 [4] and began to >>> actively test JOSM with early builds of Java 9 [5]. The current test >>> results with Java 9 are excellent as all unit tests are OK. >>> >>> During the past years the JOSM community has submitted several bug >>> reports >>> to Sun/Oracle on the public bug tracker. I don't have the exhaustive >>> list, >>> but 11 recent tickets can be found by searching "JOSM" keyword on JBS >>> [6]. >>> >>> Given this status, I wonder if JOSM can be mentioned in the Quality >>> Outreach [7], and if some of our bug reports may be considered as >>> valuable >>> in the Quality Outreach report [8]. >>> >>> Best regards, >>> Vincent, for the JOSM team >>> >>> [1] https://josm.openstreetmap.de/ >>> [2] http://wiki.openstreetmap.org/wiki/JOSM >>> [3] https://en.wikipedia.org/wiki/JOSM >>> [4] https://josm.openstreetmap.de/ticket/11390 >>> [5] https://josm.openstreetmap.de/jenkins/job/JOSM/ >>> [6] >>> >>> https://bugs.openjdk.java.net/sr/jira.issueviews:searchrequest-printable/temp/SearchRequest.html?jqlQuery=text+~+%22josm%22 >>> >>> [7] https://wiki.openjdk.java.net/display/quality/Quality+Outreach >>> [8] >>> >>> https://wiki.openjdk.java.net/display/quality/Quality+Outreach+report+Sept+%272015 >>> >> >> >> -- >> Cheers, Martijn (Sent from Gmail Mobile) >> >> >> > > -- > 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 Fri Oct 9 08:18:47 2015 From: rory.odonnell at oracle.com (Rory O'Donnell) Date: Fri, 9 Oct 2015 09:18:47 +0100 Subject: Early Access build 83 for JDK 9 and JDK 9 with Project Jigsaw are available for download. Message-ID: <56177867.6000905@oracle.com> Hi All, JDK 9 with Project Jigsaw Early Access build b83 is available for download at jdk9.java.net/jigsaw . Notable changes: * The -Xoverride option has been extended and renamed to -Xpatch, and the -XaddReads option has been restored [1] (changesets 04dd0430530e, 095fc622bf01). * ClassLoader::getPackage now works as it did previously, walking the class-loader hierarchy in order to find Package objects, which enables NetBeans to start up [2] (5805781b9370). * Class::getResource will now return a URL to a resource in a module, when invoked from code within that module (0fbe4c72638a). * The big module-summary table has been improved, and will now be posted with each build [3] (e922b207c170). JDK 9 Early Access build b83 is available for download , summary of changes are listed here . * Request for G1 GC Feedback at wiki - https://wiki.openjdk.java.net/display/HotSpot/G1GC+Feedback * This wiki-page aims to outline the basic JVM parameters switching to G1GC, and how you can help collecting data comparing the G1GC and Parallel GC. Rgds, Rory [1]http://mail.openjdk.java.net/pipermail/jigsaw-dev/2015-September/004740.html [2]http://mail.openjdk.java.net/pipermail/jigsaw-dev/2015-September/004730.html [3]http://cr.openjdk.java.net/~mr/jigsaw/ea/module-summary.html -- 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 Mon Oct 19 09:38:04 2015 From: rory.odonnell at oracle.com (Rory O'Donnell) Date: Mon, 19 Oct 2015 10:38:04 +0100 Subject: JDK 9 early access b85 test results now available Message-ID: <5624B9FC.60007@oracle.com> Hi All, JDK 9 ea b85 test results are now available at http://www.java.net/download/openjdk/testresults/9/testresults.html The jdk test results contain 15 differences from the b84 test results. Three new testcase failures are under investigation. The hotspot test results contain 4 differences from the b84 test results. No new testcase failures found. The langtools test results contain 9 differences from the b84 test results. Three new testcase failures are under investigation. The nashorn test result is available at http://download.java.net/openjdk/testresults/9/archives/b85/emailable-report.html -- Rgds,Rory O'Donnell Quality Engineering Manager Oracle EMEA , Dublin, Ireland -------------- next part -------------- An HTML attachment was scrubbed... URL: From martijnverburg at gmail.com Sat Oct 24 21:58:00 2015 From: martijnverburg at gmail.com (Martijn Verburg) Date: Sat, 24 Oct 2015 14:58:00 -0700 Subject: Quality Outreach - the old list of hosted projects at Cloudbees Message-ID: Hi all, We have a list of projects that we were building against the latest Java 8 and Java 9 binaries: https://adopt-openjdk.ci.cloudbees.com/ This list is pretty much superseded but the quality outreach efforts and it's also unrealistic for us to maintain the builds for other OSS projects (they should just have their own CI). I'm looking to get this cleaned up. I'm looking for volunteer(s) to help me contact each of the projects on the cloudbees list, assist them in getting a nightly build set up on their own CI and get them to contact Rory and his quality group to be added to that matrix. I estimate that there's only ~40 projects to migrate, so hopefully only a few each if we get enough volunteers (hint, hint) :-). We'll then keep the cloudbees instance for building OpenJDK binaries for various esoteric forests as well as the OpenJDK tools as that fits our Adoption remit far better. Cheers, Martijn -------------- next part -------------- An HTML attachment was scrubbed... URL: From martijnverburg at gmail.com Sat Oct 24 22:48:13 2015 From: martijnverburg at gmail.com (Martijn Verburg) Date: Sat, 24 Oct 2015 15:48:13 -0700 Subject: Quality Outreach - the old list of hosted projects at Cloudbees In-Reply-To: References: Message-ID: Further to this there was another older thread about getting the Fedora and Debian package maintainers involved in the quality outreach. If anyone has up to date contact details for them then let Rory know. Cheers, Martijn On 24 October 2015 at 14:58, Martijn Verburg wrote: > Hi all, > > We have a list of projects that we were building against the latest Java 8 > and Java 9 binaries: > > https://adopt-openjdk.ci.cloudbees.com/ > > This list is pretty much superseded but the quality outreach efforts and > it's also unrealistic for us to maintain the builds for other OSS > projects (they should just have their own CI). > > I'm looking to get this cleaned up. I'm looking for volunteer(s) to help > me contact each of the projects on the cloudbees list, assist them in > getting a nightly build set up on their own CI and get them to contact Rory > and his quality group to be added to that matrix. > > I estimate that there's only ~40 projects to migrate, so hopefully only a > few each if we get enough volunteers (hint, hint) :-). > > We'll then keep the cloudbees instance for building OpenJDK binaries for > various esoteric forests as well as the OpenJDK tools as that fits our > Adoption remit far better. > > > > Cheers, > Martijn > -------------- next part -------------- An HTML attachment was scrubbed... URL: From sadhak001 at gmail.com Sun Oct 25 20:41:47 2015 From: sadhak001 at gmail.com (Mani Sarkar) Date: Sun, 25 Oct 2015 20:41:47 +0000 Subject: Quality Outreach - the old list of hosted projects at Cloudbees In-Reply-To: References: Message-ID: This has been on my to do list for a long time - to contact those 40 projects and more but I think everyone else can pick atleast one of these and help us out. +1 for Debian, Fedora and other distros to bring into our fold. Cheers Mani On Sat, Oct 24, 2015 at 11:48 PM, Martijn Verburg wrote: > Further to this there was another older thread about getting the Fedora and > Debian package maintainers involved in the quality outreach. If anyone has > up to date contact details for them then let Rory know. > > Cheers, > Martijn > > On 24 October 2015 at 14:58, Martijn Verburg > wrote: > > > Hi all, > > > > We have a list of projects that we were building against the latest Java > 8 > > and Java 9 binaries: > > > > https://adopt-openjdk.ci.cloudbees.com/ > > > > This list is pretty much superseded but the quality outreach efforts and > > it's also unrealistic for us to maintain the builds for other OSS > > projects (they should just have their own CI). > > > > I'm looking to get this cleaned up. I'm looking for volunteer(s) to help > > me contact each of the projects on the cloudbees list, assist them in > > getting a nightly build set up on their own CI and get them to contact > Rory > > and his quality group to be added to that matrix. > > > > I estimate that there's only ~40 projects to migrate, so hopefully only a > > few each if we get enough volunteers (hint, hint) :-). > > > > We'll then keep the cloudbees instance for building OpenJDK binaries for > > various esoteric forests as well as the OpenJDK tools as that fits our > > Adoption remit far better. > > > > > > > > Cheers, > > Martijn > > > -- @theNeomatrix369 * | **Blog ** | *LJC Associate & LJC Advocate (@adoptopenjdk & @adoptajsr programs) *Meet-a-Project - *MutabilityDetector * | **Bitbucket * * | **Github * * | **LinkedIn * *Come to Devoxx UK 2016:* http://www.devoxx.co.uk/ *Don't chase success, rather aim for "Excellence", and success will come chasing after you!* -------------- next part -------------- An HTML attachment was scrubbed... URL: From martijnverburg at gmail.com Mon Oct 26 14:04:29 2015 From: martijnverburg at gmail.com (Martijn Verburg) Date: Mon, 26 Oct 2015 07:04:29 -0700 Subject: Quality Outreach - the old list of hosted projects at Cloudbees In-Reply-To: References: Message-ID: Hey Chris, Jitwatch is one of the ones I'm very happy to keep at cloudbees since its closely aligned / came out of this group :-) Cheers, Martijn On Monday, 26 October 2015, Chris Newland wrote: > Hi Martijn, > > I'm fine if you want to drop JITWatch from the Adopt cloudbees. > > I'll start building it on my VPS that already bakes nightlies for OpenJFX > / JDK 8 / JDK 9. > > Probably a good idea as now I can build+test against the bleeding edge and > report back to quality outreach. > > Cheers, > > Chris > @chriswhocodes > > > On Sat, October 24, 2015 21:58, Martijn Verburg wrote: > > Hi all, > > > > > > We have a list of projects that we were building against the latest Java > > 8 > > and Java 9 binaries: > > > > https://adopt-openjdk.ci.cloudbees.com/ > > > > > > This list is pretty much superseded but the quality outreach efforts and > > it's also unrealistic for us to maintain the builds for other OSS > projects > > (they should just have their own CI). > > > > > > I'm looking to get this cleaned up. I'm looking for volunteer(s) to help > > me contact each of the projects on the cloudbees list, assist them in > > getting a nightly build set up on their own CI and get them to contact > > Rory > > and his quality group to be added to that matrix. > > > > I estimate that there's only ~40 projects to migrate, so hopefully only a > > few each if we get enough volunteers (hint, hint) :-). > > > > We'll then keep the cloudbees instance for building OpenJDK binaries for > > various esoteric forests as well as the OpenJDK tools as that fits our > > Adoption remit far better. > > > > > > > > > > Cheers, > > Martijn > > > > > > > -- Cheers, Martijn (Sent from Gmail Mobile) -------------- next part -------------- An HTML attachment was scrubbed... URL: From abdul.kolarkunnu at oracle.com Tue Oct 27 15:16:36 2015 From: abdul.kolarkunnu at oracle.com (Abdul Kolarkunnu) Date: Tue, 27 Oct 2015 08:16:36 -0700 (PDT) Subject: JDK 9 b88 and JDK 8u72 b04 test results now available In-Reply-To: <7346d8b0-04d4-4c2b-ac0b-7abe36819b7b@default> References: <551A6BB1.7030503@oracle.com> <562F4D4D.8010509@oracle.com> <7346d8b0-04d4-4c2b-ac0b-7abe36819b7b@default> Message-ID: <9ba07491-5175-419e-bae8-98485491dfc8@default> ? ? JDK 9 ea b88 test results are now available at http://www.java.net/download/openjdk/testresults/9/testresults.html The jdk test results contain 39 differences from the b85 test results. There are 17 testcase failures, these failures are under investigation. 0: /home/jtest/merge9/b85/jdk/JTwork? pass: 5,238; fail: 11; error: 1; not run: 1,867 1: /home/jtest/merge9/b88/jdk/JTwork? pass: 5,243; fail: 25; error: 1; not run: 1,866 ? 0????? 1????? Test pass?? fail?? com/sun/awt/SecurityWarning/GetSizeShouldNotReturnZero.java pass?? fail?? com/sun/awt/Translucency/WindowOpacity.java pass?? fail?? com/sun/java/swing/plaf/windows/8016551/bug8016551.java pass?? fail?? java/beans/PropertyEditor/6380849/TestPropertyEditor.java pass?? fail?? java/beans/PropertyEditor/TestColorClass.java pass?? fail?? java/beans/PropertyEditor/TestColorClassJava.java pass?? fail?? java/beans/PropertyEditor/TestColorClassNull.java pass?? fail?? java/beans/PropertyEditor/TestColorClassValue.java pass?? fail?? java/beans/PropertyEditor/TestFontClass.java pass?? fail?? java/beans/PropertyEditor/TestFontClassJava.java pass?? fail?? java/beans/PropertyEditor/TestFontClassNull.java pass?? fail?? java/beans/PropertyEditor/TestFontClassValue.java pass? ?fail?? java/beans/XMLEncoder/java_awt_ScrollPane.java pass?? fail?? java/io/BufferedInputStream/CloseStream.java pass?? fail?? java/io/Serializable/unresolvableObjectStreamClass/UnresolvableObjectStreamClass.java fail?? pass?? java/util/Objects/CheckIndex.java ---??? pass?? java/util/WeakHashMap/GCDuringIteration.java ---??? pass?? java/util/concurrent/ArrayBlockingQueue/IteratorConsistency.java ---??? pass?? java/util/concurrent/BlockingQueue/DrainToFails.java ---??? pass?? java/util/concurrent/ConcurrentLinkedQueue/RemoveLeak.java ---??? pass?? java/util/concurrent/FutureTask/DoneMeansDone.java ---??? pass?? java/util/concurrent/ScheduledThreadPoolExecutor/GCRetention.java ---??? pass?? java/util/concurrent/ScheduledThreadPoolExecutor/ZeroCoreThreads.java ---??? pass?? java/util/concurrent/ThreadPoolExecutor/FlakyThreadFactory.java ---??? pass?? java/util/concurrent/ThreadPoolExecutor/ThreadRestarts.java ---??? pass?? java/util/concurrent/locks/Lock/CheckedLockLoops.java ---??? pass?? java/util/concurrent/locks/LockSupport/ParkLoops.java ---??? pass?? java/util/logging/LogManager/Configuration/updateConfiguration/HandlersOnComplexResetUpdate.java ---??? pass?? java/util/logging/LogManager/Configuration/updateConfiguration/HandlersOnComplexUpdate.java ---?? ?pass?? java/util/logging/LogManager/Configuration/updateConfiguration/SimpleUpdateConfigWithInputStreamTest.java ---??? pass?? java/util/logging/LogManager/Configuration/updateConfiguration/SimpleUpdateConfigurationTest.java ---??? pass?? java/util/logging/LogManager/Configuration/updateConfiguration/UpdateConfigurationTest.java ---??? pass?? java/util/zip/ZipFile/ZipEntryFreeTest.java pass?? fail?? javax/accessibility/AccessibilityProvider/basic.sh pass?? fail?? javax/sound/midi/Devices/InitializationHang.java ---??? pass?? javax/xml/bind/jxc/8073519/SchemagenErrorReporting.java fail?? pass?? sun/security/pkcs11/Provider/LoginISE.java fail?? pass?? sun/security/util/DerValue/BadValue.java ---??? pass?? sun/util/resources/TimeZone/Bug8139107.java ? 39 differences The hotspot test results contain 1 difference from the b85 test results. There is 1 testcase failure, this failure is under investigation. 0: /home/jtest/merge9/b85/hotspot/JTwork? pass: 885; error: 3; not run: 35 1: /home/jtest/merge9/b88/hotspot/JTwork? pass: 884; fail: 1; error: 3; not run: 35 ? 0????? 1????? Test pass?? fail?? gc/TestNUMAPageSize.java ? 1 differences The langtools test results contain 9 differences from the b85 test results. No new testcase failures found. 0: /home/jtest/merge9/b85/langtools/JTwork? pass: 3,281; fail: 3; error: 1; not run: 16 1: /home/jtest/merge9/b88/langtools/JTwork? pass: 3,290; not run: 16 ? 0????? 1????? Test ---??? pass?? tools/javac/8138840/T8138840.java ---??? pass?? tools/javac/8138840/T8139243.java ---??? pass?? tools/javac/8138840/T8139249.java fail?? pass?? tools/javac/AnonymousClass/CtorAccessBypassTest.java ---??? pass?? tools/javac/T8000316/T8000316.java fail?? pass?? tools/javac/generics/diamond/neg/Neg18.java error? pass?? tools/javac/lambda/MethodHandleInvokeTest.java ---??? pass?? tools/javac/lambda/methodReference/MethodRefIntColonColonNewTest.java fail?? pass?? tools/javac/warnings/DeprecationSE8Test.java ? 9 differences The nashorn test result is available at http://download.java.net/openjdk/testresults/9/archives/b88/emailable-report.html JDK 8u72 ea b04 test results are now available at http://www.java.net/download/openjdk/testresults/8/testresults.html The jdk test results contain 6 differences from the b02 test results. No new testcase failures found. 0: /home/jtest/merge8/jdk8u72-b02/jdk/JTwork? pass: 4,878; fail: 29; error: 2; not run: 1,054 1: /home/jtest/merge8/jdk8u72-b04/jdk/JTwork? pass: 4,884; fail: 27; error: 1; not run: 1,054 ? 0????? 1????? Test ---??? pass?? java/io/ObjectInputStream/TestObjectStreamClass.java fail?? pass?? java/lang/management/ThreadMXBean/AllThreadIds.java error? pass?? java/lang/management/ThreadMXBean/ThreadInfoArray.java ---??? pass?? java/net/InetAddress/getOriginalHostName.java fail?? pass?? java/security/KeyStore/CheckInputStream.java ---??? pass?? javax/xml/jaxp/transform/8079323/TemplatesTest.java ? 6 differences The hotspot test results contain 2 differences from the b02 test results. No new testcase failures found. 0: /home/jtest/merge8/jdk8u72-b02/hotspot/JTwork? pass: 640; fail: 40; error: 3; not run: 18 1: /home/jtest/merge8/jdk8u72-b04/hotspot/JTwork? pass: 642; fail: 38; error: 3; not run: 18 ? 0??? ??1????? Test fail?? pass?? compiler/escapeAnalysis/TestEABadMergeMem.java fail?? pass?? runtime/Thread/TestThreadDumpMonitorContention.java ? 2 differences The langtools test results contain 6 differences from the b02 test results. No new testcase failures found. 0: /home/jtest/merge8/jdk8u72-b02/langtools/JTwork? pass: 3,090; error: 4; not run: 7 1: /home/jtest/merge8/jdk8u72-b04/langtools/JTwork? pass: 3,092; error: 2; not run: 7 ? 0????? 1????? Test pass?? error? tools/javac/lambda/MethodReference12.java error? pass?? tools/javac/lambda/bridge/TestMetafactoryBridges.java error? pass?? tools/javac/lambda/intersection/IntersectionTargetTypeTest.java error? pass?? tools/javac/nio/compileTest/CompileTest.java pass?? error? tools/javac/processing/errors/CrashOnNonExistingAnnotation/Source.java error? pass?? tools/javac/varargs/warning/Warn4.java ? 6 differences The nashorn test result is available at http://download.java.net/openjdk/testresults/8/archives8/jdk8u72-b04/emailable-report.html ? -- Regards, Abdul Muneer Quality Engineer Oracle, Bangalore, India ? ? -------------- next part -------------- An HTML attachment was scrubbed... URL: From abdul.kolarkunnu at oracle.com Thu Oct 29 17:09:33 2015 From: abdul.kolarkunnu at oracle.com (Muneer Kolarkunnu) Date: Thu, 29 Oct 2015 10:09:33 -0700 (PDT) Subject: JDK 8u72 b05 test results now available In-Reply-To: <7544700e-9163-4c93-9023-d386e4f8187c@default> References: <7544700e-9163-4c93-9023-d386e4f8187c@default> Message-ID: <547db2b0-3457-4294-b991-5fb04e823a99@default> JDK 8u72 ea b05 test results are now available at http://www.java.net/download/openjdk/testresults/8/testresults.html The jdk test results contain 2 differences from the b04 test results. No new testcase failures found. 0: /home/jtest/merge8/jdk8u72-b04/jdk/JTwork pass: 4,884; fail: 27; error: 1; not run: 1,054 1: /home/jtest/merge8/jdk8u72-b05/jdk/JTwork pass: 4,886; fail: 27; error: 1; not run: 1,056 0 1 Test --- pass java/util/zip/ZipFile/ZipEntryFreeTest.java --- pass javax/xml/bind/jxc/8073519/SchemagenErrorReporting.java 2 differences The hotspot test results contain 0 differences from the b04 test results. The langtools test results contain 5 differences from the b04 test results. No new testcase failures found. 0: /home/jtest/merge8/jdk8u72-b04/langtools/JTwork pass: 3,092; error: 2; not run: 7 1: /home/jtest/merge8/jdk8u72-b05/langtools/JTwork pass: 3,091; error: 3; not run: 7 0 1 Test pass error tools/javac/T6407257.java error pass tools/javac/lambda/MethodReference12.java pass error tools/javac/lambda/bridge/TestMetafactoryBridges.java pass error tools/javac/lambda/lambdaExpression/SamConversionComboTest.java error pass tools/javac/processing/errors/CrashOnNonExistingAnnotation/Source.java 5 differences The nashorn test result is available at http://download.java.net/openjdk/testresults/8/archives8/jdk8u72-b05/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 Oct 30 15:02:59 2015 From: rory.odonnell at oracle.com (Rory O'Donnell) Date: Fri, 30 Oct 2015 15:02:59 +0000 Subject: Early Access builds for JDK 8u72 b05 , JDK 9 b88 and JDK 9 with Project Jigsaw build b86 are available on java.net Message-ID: <563386A3.30503@oracle.com> Hi All, Early Access build for JDK 8u72 b05 is available on java.net, summary of changes are listed here. Early Access build for JDK 9 b88 is available on java.net, summary of changes are listed here . Early Access build for JDK 9 with Project Jigsaw b86 is available on java.net. Changes for JDK 9 with Project Jigsaw b86 : - * New options for the jdeps tool: -genmoduleinfo to generate draft module-info.java files, and -ct to do a compile-time analysis of references (i.e., follow all references leaving all classes in each referenced JAR file) rather than the default run-time analysis (which only follows references leaving referenced classes). * jlink no longer does service binding by default. * Class::getPackage fixed to return null for array types, primitives, and void (bug reported by Chris Newland). * Improved messages in IllegalAccessExceptions thrown by core reflection. * java -verbose now works with -Xpatch . * The special token ALL-SYSTEM can be used with the -addmods option to add all system modules. * New methods Module::{addUses,canUse}, which are dynamic equivalents of service-use clauses in module declarations. Rgds, Rory -- Rgds,Rory O'Donnell Quality Engineering Manager Oracle EMEA , Dublin, Ireland -------------- next part -------------- An HTML attachment was scrubbed... URL: From vincent at josm.openstreetmap.de Fri Oct 30 15:29:23 2015 From: vincent at josm.openstreetmap.de (Vincent Privat) Date: Fri, 30 Oct 2015 16:29:23 +0100 Subject: JOSM feedback on Java 7,8,9, including Jigsaw EA Message-ID: Hi, Following the recent inclusion of JOSM to the Quality Outreach list by the Adoption Group, we have compiled every single Java issue we have encountered, and reported when it was new, for the latest versions of Java, on a single page: https://josm.openstreetmap.de/wiki/JavaBugs We will use this page to coordinate our communication efforts with you. Is it possible to add a link to it in the last column of the Quality Outreach table? The list currently contains 29 unresolved items and 18 resolved ones. I won't go through all of them in this e-mail. Ideally we'd like to see all of them fixed in a future Java release but I will only focus on the most important ones. Concerning Jigsaw: - We have reported 3 bugs. All made it to the public JIRA: 8138878, 8140477, 8140481. The second one is a bit problematic for our tests as it basically kills our Jenkins instance. I see the two other ones are understood/in progress. We will do more tests after we resolve the hanging problem. - We'd like to know if it can be expected to see the package sun.security.x509 become a public JDK API, for example in javax.security.cert? We currently use it to generate a self-signed certificate in order to create a local https server. That's our only use of private JDK API. Concerning Valhalla: - I see some discussions about building the JDK with project Valhalla. Are you going to provide public Early Access builds like project Jigsaw? Concerning the JIRA database: - Is it possible to add the label "josm-found" to issues 8140481, 8139659, 8034224, 7158257, 7194099 ? - Some issues didn't make it to the public JIRA and remained in the private bug database. Can we please have more information on them (why have they apparently been rejected)? The incident numbers are JI-9009025, JI-9010791, JI-9009449, JI-9008003. - Is it expected to allow external people to have the possibility to subscribe to JDK issues? Concerning our incoming migration from Java 7 to Java 8: - I am concerned about three issues in Java2D/AWT on Linux. We have several duplicate bug reports for them: 6322854, 7172749, 8098530. Can we hope for a fix in a future update of Java 8? Finally: - We had a terrible experience when trying to report a bug against JAXP. We detected a severe data corruption problem in StaX when dealing with Unicode SMP characters, so we reported it, including a sample Java program 100% reproducible, in January 2013 (JAXP-76 on java.net JIRA). As no activity was visible on this JIRA instance, we tried to use the standard Java bug report, three times, without success, with incident numbers 2431783 (2013-01-23), 2627098 (2013-10-28) and 9048481 (2014-11-28), without any answer. On 2014, November 29th we discovered by chance that the bug had finally been detected and fixed internally, as JDK-8058175 (created and resolved in September 2014). We reported back to the public JAXP JIRA instance, again without any answer. 6 months later we finally got the ironic and laconic answer "Please report issues to the OpenJDK Bug System", which was exactly was we were trying to do for 2 years! Can you please tell us why our bug reports were all silently ignored while the bug was real, and if is it still worth reporting bugs against JAXP? Thankfully we had far better experiences with other components of the JDK. -------------- next part -------------- An HTML attachment was scrubbed... URL: From rory.odonnell at oracle.com Fri Oct 30 15:41:20 2015 From: rory.odonnell at oracle.com (Rory O'Donnell) Date: Fri, 30 Oct 2015 15:41:20 +0000 Subject: JOSM feedback on Java 7,8,9, including Jigsaw EA In-Reply-To: References: Message-ID: <56338FA0.9040402@oracle.com> On 30/10/2015 15:29, Vincent Privat wrote: > Hi, > Following the recent inclusion of JOSM to the Quality Outreach list by > the Adoption Group, we have compiled every single Java issue we have > encountered, and reported when it was new, for the latest versions of > Java, on a single page: > > https://josm.openstreetmap.de/wiki/JavaBugs > > We will use this page to coordinate our communication efforts with > you. Is it possible to add a link to it in the last column of the > Quality Outreach table? Added to the wiki, thanks for logging all these issues. I suggest you followup with the relevant mailing lists to get specific feedback as you have done with jigsaw-dev. > > The list currently contains 29 unresolved items and 18 resolved ones. > > I won't go through all of them in this e-mail. Ideally we'd like to > see all of them fixed in a future Java release but I will only focus > on the most important ones. > > Concerning Jigsaw: > - We have reported 3 bugs. All made it to the public JIRA: 8138878, > 8140477, 8140481. The second one is a bit problematic for our tests as > it basically kills our Jenkins instance. I see the two other ones are > understood/in progress. We will do more tests after we resolve the > hanging problem. > - We'd like to know if it can be expected to see the > package sun.security.x509 become a public JDK API, for example in > javax.security.cert? We currently use it to generate a self-signed > certificate in order to create a local https server. That's our only > use of private JDK API. > > Concerning Valhalla: > - I see some discussions about building the JDK with project Valhalla. > Are you going to provide public Early Access builds like project Jigsaw? > > Concerning the JIRA database: > - Is it possible to add the label "josm-found" to > issues 8140481, 8139659, 8034224, 7158257, 7194099 ? > - Some issues didn't make it to the public JIRA and remained in the > private bug database. Can we please have more information on them (why > have they apparently been rejected)? The incident numbers > are JI-9009025, JI-9010791, JI-9009449, JI-9008003. > - Is it expected to allow external people to have the possibility to > subscribe to JDK issues? I will take a look at these and come back to you. > > Concerning our incoming migration from Java 7 to Java 8: > - I am concerned about three issues in Java2D/AWT on Linux. We have > several duplicate bug reports for them: 6322854, 7172749, 8098530. Can > we hope for a fix in a future update of Java 8? > > Finally: > - We had a terrible experience when trying to report a bug against > JAXP. We detected a severe data corruption problem in StaX when > dealing with Unicode SMP characters, so we reported it, including a > sample Java program 100% reproducible, in January 2013 (JAXP-76 on > java.net JIRA). As no activity was visible on this > JIRA instance, we tried to use the standard Java bug report, three > times, without success, with incident numbers 2431783 > (2013-01-23), 2627098 (2013-10-28) and 9048481 (2014-11-28), without > any answer. On 2014, November 29th we discovered by chance that the > bug had finally been detected and fixed internally, as JDK-8058175 > (created and resolved in September 2014). We reported back to the > public JAXP JIRA instance, again without any answer. 6 months later we > finally got the ironic and laconic answer "Please report issues to the > OpenJDK Bug System", which was exactly was we were trying to do for 2 > years! Can you please tell us why our bug reports were all silently > ignored while the bug was real, and if is it still worth reporting > bugs against JAXP? Thankfully we had far better experiences with other > components of the JDK. I will take a look for you and see what I can find. Rgds,Rory -- Rgds,Rory O'Donnell Quality Engineering Manager Oracle EMEA , Dublin, Ireland -------------- next part -------------- An HTML attachment was scrubbed... URL: From Alan.Bateman at oracle.com Sat Oct 31 10:47:31 2015 From: Alan.Bateman at oracle.com (Alan Bateman) Date: Sat, 31 Oct 2015 10:47:31 +0000 Subject: JOSM feedback on Java 7,8,9, including Jigsaw EA In-Reply-To: References: Message-ID: <56349C43.1010601@oracle.com> On 30/10/2015 15:29, Vincent Privat wrote: > : > - Some issues didn't make it to the public JIRA and remained in the > private bug database. Can we please have more information on them (why > have they apparently been rejected)? The incident numbers > are JI-9009025, JI-9010791, JI-9009449, JI-9008003. Incidents submitted via bugs.sun.com have historically been hit or miss. I don't know why these four were not moved to the JDK bug database, but here they are now: JI-9009025 => https://bugs.openjdk.java.net/browse/JDK-8141093 JI-9010791 => https://bugs.openjdk.java.net/browse/JDK-8141094 JI-9009449 => https://bugs.openjdk.java.net/browse/JDK-8141095 JI-9008003 => https://bugs.openjdk.java.net/browse/JDK-8141096 The OpenJDK mailing lists aren't a support channel but reproducible test cases are a wonderful way to contribute. So if you have test cases or patches that can be added to these bugs for the issues that are in OpenJDK then it's best to follow-up on the appropriate mailing list (likely awt-dev or swing-dev for some of these). > : > > Finally: > - We had a terrible experience when trying to report a bug against > JAXP. We detected a severe data corruption problem in StaX when > dealing with Unicode SMP characters, so we reported it, including a > sample Java program 100% reproducible, in January 2013 (JAXP-76 on > java.net JIRA). As no activity was visible on this > JIRA instance, we tried to use the standard Java bug report, three > times, without success, with incident numbers 2431783 > (2013-01-23), 2627098 (2013-10-28) and 9048481 (2014-11-28), without > any answer. On 2014, November 29th we discovered by chance that the > bug had finally been detected and fixed internally, as JDK-8058175 > (created and resolved in September 2014). We reported back to the > public JAXP JIRA instance, again without any answer. 6 months later we > finally got the ironic and laconic answer "Please report issues to the > OpenJDK Bug System", which was exactly was we were trying to do for 2 > years! Can you please tell us why our bug reports were all silently > ignored while the bug was real, and if is it still worth reporting > bugs against JAXP? Thankfully we had far better experiences with other > components of the JDK. JAXP development moved from the jaxp.java.net project to OpenJDK in early 2012. The project main page should be clearer on this point. I wasn't aware there was a JIRA instance but it probably should be shut down to avoid confusion. In any case, here is the mapping: 2431783 => https://bugs.openjdk.java.net/browse/JDK-8132652 2627098 => this one is on the old Sun web incident reporting system, I don't know how to move it to JIRA but it seems to be a dup of JDK-8141097 or JDK-8058175. JI-9048481 => https://bugs.openjdk.java.net/browse/JDK-8141097 As you note, JDK-8058175 has been fixed in JDK 9 builds for some time (since jdk9-b31). If you can verify the fix with the JDK 9 builds then you could lobby on jdk8u-dev to have it back-ported to 8u. -Alan. -------------- next part -------------- An HTML attachment was scrubbed... URL: From sadhak001 at gmail.com Sat Oct 31 11:10:03 2015 From: sadhak001 at gmail.com (Mani Sarkar) Date: Sat, 31 Oct 2015 11:10:03 +0000 Subject: Fwd: Build failed in Jenkins: TestNG #57 In-Reply-To: <716780633.22.1446289385091.JavaMail.adopt-openjdk@jenkins-adopt-openjdk> References: <545310728.21.1446268072141.JavaMail.adopt-openjdk@jenkins-adopt-openjdk> <716780633.22.1446289385091.JavaMail.adopt-openjdk@jenkins-adopt-openjdk> Message-ID: FYI TestNG fails with latest JDK9 Build 88 (https://jdk9.java.net/download/) The authors should have already been notified, but I'll also send them a ping. Cheers, Mani ---------- Forwarded message ---------- From: Date: Sat, Oct 31, 2015 at 11:03 AM Subject: Build failed in Jenkins: TestNG #57 To: martijnverburg at gmail.com, sadhak001 at gmail.com See ------------------------------------------ [...truncated 2578 lines...] Note: Recompile with -Xlint:unchecked for details. 1 warning :processResources :classes :jar :javadoc< https://adopt-openjdk.ci.cloudbees.com/job/TestNG/ws/src/main/java/org/testng/TestNG.java>:35: error: cannot find symbol import org.testng.internal.Version; ^ symbol: class Version location: package org.testng.internal 1 warning :javadocJar :sourcesJar :signArchives SKIPPED :assemble :compileTestJavawarning: [options] bootstrap class path not set in conjunction with -source 1.7 Note: Some input files use or override a deprecated API. Note: Recompile with -Xlint:deprecation for details. Note: Some input files use unchecked or unsafe operations. Note: Recompile with -Xlint:unchecked for details. 1 warning :processTestResources :testClasses :test TestNG > Regression2 > test.groupinvocation.GroupSuiteTest.Regression2 FAILED java.lang.AssertionError at GroupSuiteTest.java:69 TestNG > Regression2 > test.groupinvocation.GroupSuiteTest.Regression2 FAILED java.lang.AssertionError at GroupSuiteTest.java:69 TestNG > Regression2 > test.groupinvocation.GroupSuiteTest.Regression2 FAILED java.lang.AssertionError at GroupSuiteTest.java:69 TestNG > Regression2 > test.groupinvocation.GroupSuiteTest.Regression2 FAILED java.lang.AssertionError at GroupSuiteTest.java:69 TestNG > Regression2 > test.groupinvocation.GroupSuiteTest.Regression2 FAILED java.lang.AssertionError at GroupSuiteTest.java:69 TestNG > Regression2 > test.groupinvocation.GroupSuiteTest.Regression2 FAILED java.lang.AssertionError at GroupSuiteTest.java:69 TestNG > Regression2 > test.groupinvocation.GroupSuiteTest.Regression2 FAILED java.lang.AssertionError at GroupSuiteTest.java:69 TestNG > Regression2 > test.annotationtransformer.AnnotationTransformerTest.Regression2 FAILED java.lang.AssertionError at AnnotationTransformerTest.java:46 TestNG > Regression2 > test.annotationtransformer.AnnotationTransformerTest.Regression2 FAILED java.lang.AssertionError at AnnotationTransformerTest.java:75 TestNG > Regression2 > test.preserveorder.PreserveOrderTest.Regression2 FAILED java.lang.AssertionError at PreserveOrderTest.java:105 TestNG > Method selectors > test.methodselectors.CommandLineTest.Method selectors FAILED java.lang.AssertionError at CommandLineTest.java:176 TestNG > Method selectors > test.methodselectors.CommandLineTest.Method selectors FAILED java.lang.AssertionError at CommandLineTest.java:176 TestNG > Method selectors > test.methodselectors.CommandLineTest.Method selectors FAILED java.lang.AssertionError at CommandLineTest.java:176 TestNG > Method selectors > test.methodselectors.CommandLineTest.Method selectors FAILED java.lang.AssertionError at CommandLineTest.java:176 TestNG > Method selectors > test.methodselectors.CommandLineTest.Method selectors FAILED java.lang.AssertionError at CommandLineTest.java:176 TestNG > Method selectors > test.methodselectors.CommandLineTest.Method selectors FAILED java.lang.AssertionError at CommandLineTest.java:176 TestNG > Method selectors > test.methodselectors.CommandLineTest.Method selectors FAILED java.lang.AssertionError at CommandLineTest.java:176 TestNG > Method selectors > test.methodselectors.CommandLineTest.Method selectors FAILED java.lang.AssertionError at CommandLineTest.java:176 TestNG > Method selectors > test.methodselectors.MethodSelectorInSuiteTest.Method selectors FAILED java.lang.AssertionError at MethodSelectorInSuiteTest.java:75 TestNG > Method selectors > test.methodselectors.MethodSelectorInSuiteTest.Method selectors FAILED java.lang.AssertionError at MethodSelectorInSuiteTest.java:75 TestNG > Method selectors > test.methodselectors.MethodSelectorInSuiteTest.Method selectors FAILED java.lang.AssertionError at MethodSelectorInSuiteTest.java:75 TestNG > JUnit > test.JUnitTest1.JUnit FAILED java.lang.AssertionError at JUnitTest1.java:36 TestNG > JUnit > test.JUnitTest1.JUnit FAILED java.lang.AssertionError at JUnitTest1.java:50 TestNG > JUnit > test.JUnitTest1.JUnit FAILED java.lang.AssertionError at JUnitTest1.java:112 TestNG > JUnit > test.JUnitTest1.JUnit FAILED java.lang.AssertionError at JUnitTest1.java:97 TestNG > JUnit > test.JUnitTest1.JUnit FAILED java.lang.AssertionError at JUnitTest1.java:134 TestNG > JUnit > test.JUnitTest1.JUnit FAILED java.lang.AssertionError at JUnitTest1.java:79 TestNG > JUnit > test.JUnitTest1.JUnit FAILED java.lang.AssertionError at JUnitTest1.java:65 TestNG > JUnit > test.CommandLineTest.JUnit FAILED java.lang.AssertionError at CommandLineTest.java:35 TestNG > JUnit > test.CommandLineTest.JUnit FAILED java.lang.AssertionError at CommandLineTest.java:125 TestNG > JUnit > test.JUnit4Test.JUnit FAILED java.lang.AssertionError at JUnit4Test.java:46 TestNG > JUnit > test.JUnit4Test.JUnit FAILED java.lang.AssertionError at JUnit4Test.java:61 TestNG > JUnit > test.JUnit4Test.JUnit FAILED java.lang.AssertionError at JUnit4Test.java:77 TestNG > JUnit > test.JUnit4Test.JUnit FAILED java.lang.AssertionError at JUnit4Test.java:92 TestNG > JUnit > test.JUnit4Test.JUnit FAILED java.lang.AssertionError at JUnit4Test.java:31 TestNG > RetryAnalyzer > test.retryAnalyzer.RetryAnalyzerTest.RetryAnalyzer FAILED java.lang.AssertionError at RetryAnalyzerTest.java:25 TestNG > MethodInterceptor > test.methodinterceptors.multipleinterceptors.MultipleInterceptorsTest.MethodInterceptor FAILED java.lang.AssertionError at MultipleInterceptorsTest.java:24 TestNG > Bug173 > test.testng173.TestNG173Test.Bug173 FAILED java.lang.AssertionError at TestNG173Test.java:39 TestNG > Bug173 > test.testng173.TestNG173Test.Bug173 FAILED java.lang.AssertionError at TestNG173Test.java:62 TestNG > Mixed > test.mixed.MixedTest.Mixed FAILED java.lang.AssertionError at MixedTest.java:44 TestNG > Mixed > test.mixed.MixedTest.Mixed FAILED java.lang.AssertionError at MixedTest.java:59 TestNG > Mixed > test.mixed.MixedTest.Mixed FAILED java.lang.AssertionError at MixedTest.java:28 1160 tests completed, 42 failed :test FAILED FAILURE: Build failed with an exception. * What went wrong: Execution failed for task ':test'. > There were failing tests. See the report at: file://< https://adopt-openjdk.ci.cloudbees.com/job/TestNG/ws/build/reports/tests/index.html > * Try: Run with --info or --debug option to get more log output. * Exception is: org.gradle.api.tasks.TaskExecutionException: Execution failed for task ':test'. at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeActions(ExecuteActionsTaskExecuter.java:69) at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.execute(ExecuteActionsTaskExecuter.java:46) at org.gradle.api.internal.tasks.execution.PostExecutionAnalysisTaskExecuter.execute(PostExecutionAnalysisTaskExecuter.java:35) at org.gradle.api.internal.tasks.execution.SkipUpToDateTaskExecuter.execute(SkipUpToDateTaskExecuter.java:64) at org.gradle.api.internal.tasks.execution.ValidatingTaskExecuter.execute(ValidatingTaskExecuter.java:58) at org.gradle.api.internal.tasks.execution.SkipEmptySourceFilesTaskExecuter.execute(SkipEmptySourceFilesTaskExecuter.java:52) at org.gradle.api.internal.tasks.execution.SkipTaskWithNoActionsExecuter.execute(SkipTaskWithNoActionsExecuter.java:52) at org.gradle.api.internal.tasks.execution.SkipOnlyIfTaskExecuter.execute(SkipOnlyIfTaskExecuter.java:53) at org.gradle.api.internal.tasks.execution.ExecuteAtMostOnceTaskExecuter.execute(ExecuteAtMostOnceTaskExecuter.java:43) at org.gradle.execution.taskgraph.DefaultTaskGraphExecuter$EventFiringTaskWorker.execute(DefaultTaskGraphExecuter.java:208) at org.gradle.execution.taskgraph.DefaultTaskGraphExecuter$EventFiringTaskWorker.execute(DefaultTaskGraphExecuter.java:186) at org.gradle.execution.taskgraph.AbstractTaskPlanExecutor$TaskExecutorWorker.processTask(AbstractTaskPlanExecutor.java:62) at org.gradle.execution.taskgraph.AbstractTaskPlanExecutor$TaskExecutorWorker.run(AbstractTaskPlanExecutor.java:50) at org.gradle.execution.taskgraph.DefaultTaskPlanExecutor.process(DefaultTaskPlanExecutor.java:25) at org.gradle.execution.taskgraph.DefaultTaskGraphExecuter.execute(DefaultTaskGraphExecuter.java:111) at org.gradle.execution.SelectedTaskExecutionAction.execute(SelectedTaskExecutionAction.java:37) at org.gradle.execution.DefaultBuildExecuter.execute(DefaultBuildExecuter.java:62) at org.gradle.execution.DefaultBuildExecuter.access$200(DefaultBuildExecuter.java:23) at org.gradle.execution.DefaultBuildExecuter$2.proceed(DefaultBuildExecuter.java:68) at org.gradle.execution.DryRunBuildExecutionAction.execute(DryRunBuildExecutionAction.java:32) at org.gradle.execution.DefaultBuildExecuter.execute(DefaultBuildExecuter.java:62) at org.gradle.execution.DefaultBuildExecuter.execute(DefaultBuildExecuter.java:55) at org.gradle.initialization.DefaultGradleLauncher$6.run(DefaultGradleLauncher.java:174) at org.gradle.internal.Factories$1.create(Factories.java:22) at org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:62) at org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:47) at org.gradle.initialization.DefaultGradleLauncher.runBuildOperation(DefaultGradleLauncher.java:189) at org.gradle.initialization.DefaultGradleLauncher.doBuildStages(DefaultGradleLauncher.java:171) at org.gradle.initialization.DefaultGradleLauncher.access$200(DefaultGradleLauncher.java:35) at org.gradle.initialization.DefaultGradleLauncher$1.create(DefaultGradleLauncher.java:104) at org.gradle.initialization.DefaultGradleLauncher$1.create(DefaultGradleLauncher.java:97) at org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:62) at org.gradle.initialization.DefaultGradleLauncher.runRootBuildOperation(DefaultGradleLauncher.java:184) at org.gradle.initialization.DefaultGradleLauncher.doBuild(DefaultGradleLauncher.java:97) at org.gradle.initialization.DefaultGradleLauncher.run(DefaultGradleLauncher.java:86) at org.gradle.launcher.exec.InProcessBuildActionExecuter$DefaultBuildController.run(InProcessBuildActionExecuter.java:93) at org.gradle.tooling.internal.provider.ExecuteBuildActionRunner.run(ExecuteBuildActionRunner.java:28) at org.gradle.launcher.exec.ChainingBuildActionRunner.run(ChainingBuildActionRunner.java:35) at org.gradle.launcher.exec.InProcessBuildActionExecuter.execute(InProcessBuildActionExecuter.java:43) at org.gradle.launcher.exec.InProcessBuildActionExecuter.execute(InProcessBuildActionExecuter.java:27) at org.gradle.launcher.exec.ContinuousBuildActionExecuter.execute(ContinuousBuildActionExecuter.java:72) at org.gradle.launcher.exec.ContinuousBuildActionExecuter.execute(ContinuousBuildActionExecuter.java:44) at org.gradle.launcher.exec.DaemonUsageSuggestingBuildActionExecuter.execute(DaemonUsageSuggestingBuildActionExecuter.java:50) at org.gradle.launcher.exec.DaemonUsageSuggestingBuildActionExecuter.execute(DaemonUsageSuggestingBuildActionExecuter.java:27) at org.gradle.launcher.cli.RunBuildAction.run(RunBuildAction.java:40) at org.gradle.internal.Actions$RunnableActionAdapter.execute(Actions.java:170) at org.gradle.launcher.cli.CommandLineActionFactory$ParseAndBuildAction.execute(CommandLineActionFactory.java:237) at org.gradle.launcher.cli.CommandLineActionFactory$ParseAndBuildAction.execute(CommandLineActionFactory.java:210) at org.gradle.launcher.cli.JavaRuntimeValidationAction.execute(JavaRuntimeValidationAction.java:35) at org.gradle.launcher.cli.JavaRuntimeValidationAction.execute(JavaRuntimeValidationAction.java:24) at org.gradle.launcher.cli.CommandLineActionFactory$WithLogging.execute(CommandLineActionFactory.java:206) at org.gradle.launcher.cli.CommandLineActionFactory$WithLogging.execute(CommandLineActionFactory.java:169) at org.gradle.launcher.cli.ExceptionReportingAction.execute(ExceptionReportingAction.java:33) at org.gradle.launcher.cli.ExceptionReportingAction.execute(ExceptionReportingAction.java:22) at org.gradle.launcher.Main.doAction(Main.java:33) at org.gradle.launcher.bootstrap.EntryPoint.run(EntryPoint.java:45) at org.gradle.launcher.bootstrap.ProcessBootstrap.runNoExit(ProcessBootstrap.java:54) at org.gradle.launcher.bootstrap.ProcessBootstrap.run(ProcessBootstrap.java:35) at org.gradle.launcher.GradleMain.main(GradleMain.java:23) at org.gradle.wrapper.BootstrapMainStarter.start(BootstrapMainStarter.java:30) at org.gradle.wrapper.WrapperExecutor.execute(WrapperExecutor.java:127) at org.gradle.wrapper.GradleWrapperMain.main(GradleWrapperMain.java:61) Caused by: org.gradle.api.GradleException: There were failing tests. See the report at: file://< https://adopt-openjdk.ci.cloudbees.com/job/TestNG/ws/build/reports/tests/index.html > at org.gradle.api.tasks.testing.Test.handleTestFailures(Test.java:1129) at org.gradle.api.tasks.testing.Test.executeTests(Test.java:567) at org.gradle.internal.reflect.JavaMethod.invoke(JavaMethod.java:75) at org.gradle.api.internal.project.taskfactory.AnnotationProcessingTaskFactory$StandardTaskAction.doExecute(AnnotationProcessingTaskFactory.java:226) at org.gradle.api.internal.project.taskfactory.AnnotationProcessingTaskFactory$StandardTaskAction.execute(AnnotationProcessingTaskFactory.java:219) at org.gradle.api.internal.project.taskfactory.AnnotationProcessingTaskFactory$StandardTaskAction.execute(AnnotationProcessingTaskFactory.java:208) at org.gradle.api.internal.AbstractTask$TaskActionWrapper.execute(AbstractTask.java:585) at org.gradle.api.internal.AbstractTask$TaskActionWrapper.execute(AbstractTask.java:568) at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeAction(ExecuteActionsTaskExecuter.java:80) at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeActions(ExecuteActionsTaskExecuter.java:61) ... 61 more BUILD FAILED Total time: 2 mins 27.355 secs Build step 'Execute shell' marked build as failure Archiving artifacts -- @theNeomatrix369 * | **Blog ** | *LJC Associate & LJC Advocate (@adoptopenjdk & @adoptajsr programs) *Meet-a-Project - *MutabilityDetector * | **Bitbucket * * | **Github * * | **LinkedIn * *Come to Devoxx UK 2016:* http://www.devoxx.co.uk/ *Don't chase success, rather aim for "Excellence", and success will come chasing after you!* -------------- next part -------------- An HTML attachment was scrubbed... URL: From sadhak001 at gmail.com Sat Oct 31 12:50:57 2015 From: sadhak001 at gmail.com (Mani Sarkar) Date: Sat, 31 Oct 2015 12:50:57 +0000 Subject: TestNG build failing with JDK9 Jigsaw due to Gradle Message-ID: Hi Rory, Do you know of a version of Gradle or a EA version which is JDK 9 Jigsaw compatible, we get these failures when building: https://adopt-openjdk.ci.cloudbees.com/view/Quality%20Outreach/job/TestNG-Jigsaw/5/console Cheers, Mani -- @theNeomatrix369 * | **Blog ** | *LJC Associate & LJC Advocate (@adoptopenjdk & @adoptajsr programs) *Meet-a-Project - *MutabilityDetector * | **Bitbucket * * | **Github * * | **LinkedIn * *Come to Devoxx UK 2016:* http://www.devoxx.co.uk/ *Don't chase success, rather aim for "Excellence", and success will come chasing after you!* -------------- next part -------------- An HTML attachment was scrubbed... URL: From vincent at josm.openstreetmap.de Sat Oct 31 13:40:22 2015 From: vincent at josm.openstreetmap.de (Vincent Privat) Date: Sat, 31 Oct 2015 14:40:22 +0100 Subject: JOSM feedback on Java 7,8,9, including Jigsaw EA In-Reply-To: <56349C43.1010601@oracle.com> References: <56349C43.1010601@oracle.com> Message-ID: Hi Alan, Thanks a lot for your answers and guidance. We will follow-up bugs with appropriate mailing lists and attach test cases every time possible. Best regards, Vincent 2015-10-31 11:47 GMT+01:00 Alan Bateman : > On 30/10/2015 15:29, Vincent Privat wrote: > > : > - Some issues didn't make it to the public JIRA and remained in the > private bug database. Can we please have more information on them (why have > they apparently been rejected)? The incident numbers > are JI-9009025, JI-9010791, JI-9009449, JI-9008003. > > > Incidents submitted via bugs.sun.com have historically been hit or miss. > I don't know why these four were not moved to the JDK bug database, but > here they are now: > > JI-9009025 => https://bugs.openjdk.java.net/browse/JDK-8141093 > > JI-9010791 => https://bugs.openjdk.java.net/browse/JDK-8141094 > > JI-9009449 => https://bugs.openjdk.java.net/browse/JDK-8141095 > > JI-9008003 => https://bugs.openjdk.java.net/browse/JDK-8141096 > > The OpenJDK mailing lists aren't a support channel but reproducible test > cases are a wonderful way to contribute. So if you have test cases or > patches that can be added to these bugs for the issues that are in OpenJDK > then it's best to follow-up on the appropriate mailing list (likely awt-dev > or swing-dev for some of these). > > > : > > Finally: > - We had a terrible experience when trying to report a bug against JAXP. > We detected a severe data corruption problem in StaX when dealing with > Unicode SMP characters, so we reported it, including a sample Java program > 100% reproducible, in January 2013 (JAXP-76 on java.net JIRA). As no > activity was visible on this JIRA instance, we tried to use the standard > Java bug report, three times, without success, with incident > numbers 2431783 (2013-01-23), 2627098 (2013-10-28) and 9048481 > (2014-11-28), without any answer. On 2014, November 29th we discovered by > chance that the bug had finally been detected and fixed internally, as > JDK-8058175 (created and resolved in September 2014). We reported back to > the public JAXP JIRA instance, again without any answer. 6 months later we > finally got the ironic and laconic answer "Please report issues to the > OpenJDK Bug System", which was exactly was we were trying to do for 2 > years! Can you please tell us why our bug reports were all silently ignored > while the bug was real, and if is it still worth reporting bugs against > JAXP? Thankfully we had far better experiences with other components of the > JDK. > > JAXP development moved from the jaxp.java.net project to OpenJDK in early > 2012. The project main page should be clearer on this point. I wasn't aware > there was a JIRA instance but it probably should be shut down to avoid > confusion. > > In any case, here is the mapping: > > 2431783 => https://bugs.openjdk.java.net/browse/JDK-8132652 > > 2627098 => this one is on the old Sun web incident reporting system, I > don't know how to move it to JIRA but it seems to be a dup of JDK-8141097 > or JDK-8058175. > > JI-9048481 => https://bugs.openjdk.java.net/browse/JDK-8141097 > > As you note, JDK-8058175 has been fixed in JDK 9 builds for some time > (since jdk9-b31). If you can verify the fix with the JDK 9 builds then you > could lobby on jdk8u-dev to have it back-ported to 8u. > > -Alan. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From Alan.Bateman at oracle.com Sat Oct 31 13:56:20 2015 From: Alan.Bateman at oracle.com (Alan Bateman) Date: Sat, 31 Oct 2015 13:56:20 +0000 Subject: TestNG build failing with JDK9 Jigsaw due to Gradle In-Reply-To: References: Message-ID: <5634C884.6040302@oracle.com> On 31/10/2015 12:50, Mani Sarkar wrote: > Hi Rory, > > Do you know of a version of Gradle or a EA version which is JDK 9 > Jigsaw compatible, we get these failures when building: > > https://adopt-openjdk.ci.cloudbees.com/view/Quality%20Outreach/job/TestNG-Jigsaw/5/console > Caused by: java.lang.IllegalAccessException: class org.gradle.internal.reflect.DirectInstantiator cannot access class com.sun.tools.javac.api.JavacTool (in module jdk.compiler) because module jdk.compiler does not export package com.sun.tools.javac.api to at org.gradle.internal.reflect.DirectInstantiator.newInstance(DirectInstantiator.java:49) ... 86 more We should at least check if there is a bug in the Gradle JIRA for this. It can be worked around by configuring the compileJava options to fork javac but you might not want to do that. The other issue with Gradle that we know about is the ClassCastException when attempting to run tests, this is tracked here: https://issues.gradle.org/browse/GRADLE-3287 -Alan. From Alan.Bateman at oracle.com Sat Oct 31 15:32:19 2015 From: Alan.Bateman at oracle.com (Alan Bateman) Date: Sat, 31 Oct 2015 15:32:19 +0000 Subject: JOSM feedback on Java 7,8,9, including Jigsaw EA In-Reply-To: References: <56349C43.1010601@oracle.com> Message-ID: <5634DF03.1000403@oracle.com> On 31/10/2015 13:40, Vincent Privat wrote: > Hi Alan, > Thanks a lot for your answers and guidance. We will follow-up bugs > with appropriate mailing lists and attach test cases every time possible. > Best regards, > Vincent > Thanks. So I think from the list of 29 issues then there are only 2 that are specific to the jigsaw EA builds. One of these is caused by the horrible hack to workaround JDK-6292739, I see you've started a thread on awt-dev about that issue. The other is the deadlock issue which is fixed for the next Jigsaw EA build. -Alan. From sadhak001 at gmail.com Sat Oct 31 16:34:54 2015 From: sadhak001 at gmail.com (Mani Sarkar) Date: Sat, 31 Oct 2015 16:34:54 +0000 Subject: How to contribute to the Adopt OpenJDK and OpenJDK ? Message-ID: Hi all, I have put together this page on how to ... https://neomatrix369.gitbooks.io/adoptopenjdk-getting-started-kit/content/en/how-to-navigate/how_to_contribute_to_adopt_openjdk_and_openjdk.html As a community we should feel free to amend the contents as per what really is meant by contributions. Anything incorrect or missing - feel free to report here or create a pull request (see https://neomatrix369.gitbooks.io/adoptopenjdk-getting-started-kit/content/en/how-to-navigate/contribute.html ). Thanks for reading and contributing. Cheers, Mani -- @theNeomatrix369 * | **Blog ** | *LJC Associate & LJC Advocate (@adoptopenjdk & @adoptajsr programs) *Meet-a-Project - *MutabilityDetector * | **Bitbucket * * | **Github * * | **LinkedIn * *Come to Devoxx UK 2016:* http://www.devoxx.co.uk/ *Don't chase success, rather aim for "Excellence", and success will come chasing after you!* -------------- next part -------------- An HTML attachment was scrubbed... URL: