From rory.odonnell at oracle.com Wed Sep 2 14:54:39 2015 From: rory.odonnell at oracle.com (Rory O'Donnell) Date: Wed, 2 Sep 2015 15:54:39 +0100 Subject: Quality Outreach Update Message-ID: <55E70DAF.50703@oracle.com> Hi All, We moved the Quality Outreach to the Quality Group earlier this year,here is a summary of the Bug logging activities over the past six months. We now have 48 FOSS Projects and their developers listed on the Wiki page, they have been regularly contacted to announce the availability of Early Access (EA) builds based on various OpenJDK Projects, and encouraged to report back any issues they found during their testing. Developers from 10 of the 48 participating projects filed 23 new issues in the JDK Bug System, more information in the table below. Priority Fixed In progress Duplicate Open Total P1 0 0 0 0 0 P2 7 2 1 0 10 P3 3 8 0 1 12 P4 0 1 0 0 1 Total Unique Issues 10 11 1 1 23 Components P1 P2 P3 P4 Total hotspot 0 5 2 1 8 core-libs 0 2 3 0 5 tools 0 3 4 0 7 xml 0 0 1 0 1 client-libs 0 0 1 0 1 javafx 0 0 1 0 1 Total Unique Issues 0 10 12 1 23 Raised in version Fixed In Progress Duplicate Open Total JDK 9 EA builds 9 9 1 0 19 JDK 8 EA updates 1 2 0 1 4 Total Unique Issues 10 11 1 1 23 The following testers who submitted significant bug reports deserve special mention: The following early testers who submitted significant bug reports deserve special mention: The following early testers who submitted significant bug reports deserve special mention: The following early testers who submitted significant bug reports deserve special menti on: * Apache Lucene * JaCoCo * Apache Groovy * Hazelcast * Apache Ant. Valuable reports were also received from : * Gradle * Jitwatch * AssertJ * Apache JMeter * ElasticSearch I expect to send the next Quality Outreach update in 6 months from now. This info will be posted on the Wiki page in the coming days. Rgds, Rory -- 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 Sep 2 16:32:20 2015 From: rory.odonnell at oracle.com (Rory O'Donnell) Date: Wed, 2 Sep 2015 17:32:20 +0100 Subject: Quality Outreach Update In-Reply-To: <55E70DAF.50703@oracle.com> References: <55E70DAF.50703@oracle.com> Message-ID: <55E72494.7020500@oracle.com> I have added this info to the wiki ,probably easier to read, I will update the wiki in six months time. Rgds,Rory On 02/09/2015 15:54, Rory O'Donnell wrote: > > Hi All, > > We moved the Quality Outreach to the Quality Group earlier this > year,here is a summary of the Bug logging activities over the past six > months. > > We now have 48 FOSS Projects and their developers listed on the Wiki > page, > they have been regularly contacted to announce the availability of > Early Access (EA) builds based on various OpenJDK Projects, and > encouraged to report back any issues they found during their testing. > > Developers from 10 of the 48 participating projects filed 23 new > issues in the JDK Bug System, more information in the table below. > > > Priority Fixed In progress Duplicate Open > Total > P1 > 0 > 0 > 0 > 0 > 0 > P2 > 7 > 2 > 1 > 0 > 10 > P3 > 3 > 8 > 0 > 1 > 12 > P4 > 0 > 1 > 0 > 0 > 1 > Total Unique Issues > 10 > 11 > 1 > 1 > 23 > > > Components > P1 > P2 > P3 > P4 > Total > hotspot > 0 > 5 > 2 > 1 > 8 > core-libs > 0 > 2 > 3 > 0 > 5 > tools > 0 > 3 > 4 > 0 > 7 > xml > 0 > 0 > 1 > 0 > 1 > client-libs > 0 > 0 > 1 > 0 > 1 > javafx > 0 > 0 > 1 > 0 > 1 > Total Unique Issues 0 > 10 > 12 > 1 > 23 > > > > Raised in version Fixed In Progress Duplicate > Open > Total > JDK 9 EA builds > 9 > 9 > 1 > 0 > 19 > JDK 8 EA updates > 1 > 2 > 0 > 1 > 4 > Total Unique Issues 10 > 11 > 1 > 1 > 23 > > > The following testers who submitted significant bug reports deserve > special mention: > The following early testers who submitted significant bug reports > deserve special mention: > The following early testers who submitted significant bug reports > deserve special mention: > The following early testers who submitted significant bug reports > deserve special menti > on: > > * Apache Lucene > * JaCoCo > * Apache Groovy > * Hazelcast > * Apache Ant. > > Valuable reports were also received from : > > * Gradle > * Jitwatch > * AssertJ > * Apache JMeter > * ElasticSearch > > I expect to send the next Quality Outreach update in 6 months from > now. This info will be posted on > the Wiki > page > in the coming days. > > Rgds, Rory > > -- > 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 rory.odonnell at oracle.com Wed Sep 9 17:08:57 2015 From: rory.odonnell at oracle.com (Rory O'Donnell) Date: Wed, 9 Sep 2015 18:08:57 +0100 Subject: Project Jigsaw: Early-Access Builds available on jdk9.java.net/jigsaw Message-ID: <55F067A9.6070606@oracle.com> Hi All, Early-access builds of JDK 9 with Project Jigsaw are available for download at jdk9.java.net/jigsaw . The EA builds contain the latest prototype implementation of JSR 376 , the Java Platform Module System, as well as that of the JDK-specific APIs and tools described in JEP 261 . If you'd like to try out the EA builds, by far the most helpful things you can do are: * Try to run existing applications, without change, on these builds to see whether the module system, or the modularization of the platform, breaks your code or identifies code that depends upon JDK-internal APIs or other unspecified aspects of the platform. * Experiment with the module system itself, perhaps by following the quick start guide , and start thinking about how to migrate existing libraries and application components to modules. We hope to publish some specific migration tips shortly. Please send usage questions and experience reports to the jigsaw-dev list. Specific suggestions about the design of the module system should be sent to the JSR 376 Expert Group's comments list . For more information please seen Mark Reinhold's mail [1] Rgds,Rory [1]http://mail.openjdk.java.net/pipermail/jigsaw-dev/2015-September/004480.html -- Rgds,Rory O'Donnell Quality Engineering Manager Oracle EMEA , Dublin, Ireland -------------- next part -------------- An HTML attachment was scrubbed... URL: From sadhak001 at gmail.com Wed Sep 9 18:15:59 2015 From: sadhak001 at gmail.com (Mani Sarkar) Date: Wed, 9 Sep 2015 19:15:59 +0100 Subject: Project Jigsaw: Early-Access Builds available on jdk9.java.net/jigsaw In-Reply-To: <55F067A9.6070606@oracle.com> References: <55F067A9.6070606@oracle.com> Message-ID: Thats great Rory, thanks for the heads up - I have shared it with the respective communities. Cheers. Mani On Wed, Sep 9, 2015 at 6:08 PM, Rory O'Donnell wrote: > > Hi All, > > Early-access builds of JDK 9 with Project Jigsaw are available for > download at jdk9.java.net/jigsaw . > > The EA builds contain the latest prototype implementation of JSR 376 < > http://openjdk.java.net/projects/jigsaw/spec>, the Java Platform Module > System, > as well as that of the JDK-specific APIs and tools described in JEP 261 < > http://openjdk.java.net/jeps/261>. > > If you'd like to try out the EA builds, by far the most helpful things you > can do are: > > * > > Try to run existing applications, without change, on these builds to > see whether the module system, or the modularization of the > platform, breaks your code or identifies code that depends upon > JDK-internal APIs or other unspecified aspects of the platform. > > * > > Experiment with the module system itself, perhaps by following the > quick start guide > , and start > thinking about how to migrate existing libraries and application > components to modules. We hope to publish some specific migration > tips shortly. > > Please send usage questions and experience reports to the jigsaw-dev < > http://mail.openjdk.java.net/mailman/listinfo/jigsaw-dev> list. Specific > suggestions about the design of the module system should be sent to the JSR > 376 Expert Group's comments list jpms-spec-comments at openjdk.java.net>. > > For more information please seen Mark Reinhold's mail [1] > > Rgds,Rory > > [1] > http://mail.openjdk.java.net/pipermail/jigsaw-dev/2015-September/004480.html > > -- > Rgds,Rory O'Donnell > Quality Engineering Manager > Oracle EMEA , Dublin, Ireland > > -- @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 Thu Sep 10 16:15:11 2015 From: sadhak001 at gmail.com (Mani Sarkar) Date: Thu, 10 Sep 2015 17:15:11 +0100 Subject: Project Jigsaw: Early-Access Builds available on jdk9.java.net/jigsaw In-Reply-To: References: <55F067A9.6070606@oracle.com> Message-ID: Hi Rory, I have played with the Jigsaw JDK using the Quick starter guide and have this to share with our community: https://github.com/neomatrix369/jdk9-jigsaw There is a small mistake in the example on Services (see my implementation you will spot it soon), also the Services example explains more than one concept at a time and I think this might just be a bit more than a simple example to illustrate Jigsaw features. The last two examples are not fully fleshed out. I would put a footnote about jlink, that jmod + tools are going to supersede jimage (if from what I have read so far is correct, I have even seen this mentioned on a JBUG issue). Any feedback please send my way. Cheers, Mani On Wed, Sep 9, 2015 at 7:15 PM, Mani Sarkar wrote: > Thats great Rory, thanks for the heads up - I have shared it with the > respective communities. > > Cheers. > Mani > > On Wed, Sep 9, 2015 at 6:08 PM, Rory O'Donnell > wrote: > >> >> Hi All, >> >> Early-access builds of JDK 9 with Project Jigsaw are available for >> download at jdk9.java.net/jigsaw . >> >> The EA builds contain the latest prototype implementation of JSR 376 < >> http://openjdk.java.net/projects/jigsaw/spec>, the Java Platform Module >> System, >> as well as that of the JDK-specific APIs and tools described in JEP 261 < >> http://openjdk.java.net/jeps/261>. >> >> If you'd like to try out the EA builds, by far the most helpful things >> you can do are: >> >> * >> >> Try to run existing applications, without change, on these builds to >> see whether the module system, or the modularization of the >> platform, breaks your code or identifies code that depends upon >> JDK-internal APIs or other unspecified aspects of the platform. >> >> * >> >> Experiment with the module system itself, perhaps by following the >> quick start guide >> , and start >> thinking about how to migrate existing libraries and application >> components to modules. We hope to publish some specific migration >> tips shortly. >> >> Please send usage questions and experience reports to the jigsaw-dev < >> http://mail.openjdk.java.net/mailman/listinfo/jigsaw-dev> list. Specific >> suggestions about the design of the module system should be sent to the JSR >> 376 Expert Group's comments list > jpms-spec-comments at openjdk.java.net>. >> >> For more information please seen Mark Reinhold's mail [1] >> >> Rgds,Rory >> >> [1] >> http://mail.openjdk.java.net/pipermail/jigsaw-dev/2015-September/004480.html >> >> -- >> Rgds,Rory O'Donnell >> Quality Engineering Manager >> Oracle EMEA , Dublin, Ireland >> >> > > > -- > @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!* > -- @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 Alan.Bateman at oracle.com Thu Sep 10 20:30:19 2015 From: Alan.Bateman at oracle.com (Alan Bateman) Date: Thu, 10 Sep 2015 21:30:19 +0100 Subject: Project Jigsaw: Early-Access Builds available on jdk9.java.net/jigsaw In-Reply-To: References: <55F067A9.6070606@oracle.com> Message-ID: <55F1E85B.3040004@oracle.com> On 10/09/2015 17:15, Mani Sarkar wrote: > Hi Rory, > > I have played with the Jigsaw JDK using the Quick starter guide and > have this to share with our community: > https://github.com/neomatrix369/jdk9-jigsaw > > There is a small mistake in the example on Services (see my > implementation you will spot it soon), also the Services example > explains more than one concept at a time and I think this might just > be a bit more than a simple example to illustrate Jigsaw features. > > The last two examples are not fully fleshed out. I would put a > footnote about jlink, that jmod + tools are going to supersede jimage > (if from what I have read so far is correct, I have even seen this > mentioned on a JBUG issue). > I don't immediately see the error in the services example (I need to look closer) but I think you have a point that this example jumps ahead too much. Good idea to get the examples into a repo with scripts. Just on the tools then jlink + jmod don't supersede the jimage tool. Lots of new j- tools so the following might be helpful: jlink is the linker. It links a set of modules together to create a run-time image, the layout of which is described in JEP 220. The jlink tool is in the current EA builds but no documentation to point at yet. There will be a JEP in time (as mentioned already in JEP 261). The jlink example you see in the quick start page should work and create a run-time image that contains module com.greetings and its transitive dependences. Another thing to mention is that the jigsaw/jake builds invoke jlink to create the JDK, JRE, and compact profile images. I think of jlink as a tool for the advanced tool chain and not something that most developers will use directly. The jmod tool is to the JMOD format as the jar tool is to the JAR format. In the jigsaw/jake build then you'll see that the tool is used to create a JMOD for each standard and JDK-specific module. The directory of JMOD files then serves as the module path for the linker when it creates the JDK and JRE images. Like jlink then I don't expect too many developers to need to use the jmod tool or JMOD format as modular JAR files will do just fine for most modules. In the example in the quick start page then the only reason that the JDK jmods directory is on the module path is because creating a custom image requires resolving standard and maybe JDK modules so the tool needs to be able to locate the corresponding module artifacts. Now jimage. In a run-time image (JEP 220) then classes and resources are stored in a container that is in jimage format. The format is deliberated not documented and best to assume it will change and evolve over time as it inhales new optimizations. Introducing a new container format is a bit scary and needs some tooling to aid troubleshooting in the event of problems. This is why the JDK 9 builds and the EA builds have a jimage tool. It can be used to do some verification, list or extract the contents. It's not meant to be on par with the jar tool of course. Instead just think of the jimage tool as First Aid Kit hanging on the wall in the event that you might need it. -Alan. From sadhak001 at gmail.com Thu Sep 10 21:21:59 2015 From: sadhak001 at gmail.com (Mani Sarkar) Date: Thu, 10 Sep 2015 22:21:59 +0100 Subject: Project Jigsaw: Early-Access Builds available on jdk9.java.net/jigsaw In-Reply-To: <55F1ED8E.3000904@oracle.com> References: <55F067A9.6070606@oracle.com> <55F1E85B.3040004@oracle.com> <55F1ED8E.3000904@oracle.com> Message-ID: Hi Alan, Thanks for the detailed explanation and it would be great to find this in your docs - I will link to it. The reasons I understood, jimage might go away, as I read this https://bugs. *openjdk*.java.net/browse/JDK-8049369. But now its clear, they both have their place - I did think of jimage as the runtime container - thanks for confirming Cheers, Mani On Thu, Sep 10, 2015 at 9:52 PM, Jim Connors wrote: > On 9/10/2015 4:30 PM, Alan Bateman wrote: > > I don't immediately see the error in the services example (I need to look > closer) but I think you have a point that this example jumps ahead too > much. Good idea to get the examples into a repo with scripts. > > > In the Services Section: > http://openjdk.java.net/projects/jigsaw/quick-start#services > > $ cat src/com.greetings/com/greetings/Main.java > package com.greetings; > > import com.socket.NetworkSocket; > > public class Main { > public static void main(String[] args) { > NetworkSocket s = NetworkSocket.open(); > } > } > > When you run the com.greetings.Main class via: > > $ java -mp mods -m com.greetings/com.greetings.Main > > The Quick Start guide shows the output as: > > class org.fastsocket.FastNetworkSocket > > The Main.java file referenced above prints nothing (at least in my case), > would it have to be modified slightly, something like: > > $ cat src/com.greetings/com/greetings/Main.java > package com.greetings; > > import com.socket.NetworkSocket; > > public class Main { > public static void main(String[] args) { > NetworkSocket s = NetworkSocket.open(); > System.out.println(s.getClass().toString()); > } > } > > -- Jim C > -- @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 Alan.Bateman at oracle.com Fri Sep 11 07:53:44 2015 From: Alan.Bateman at oracle.com (Alan Bateman) Date: Fri, 11 Sep 2015 08:53:44 +0100 Subject: Project Jigsaw: Early-Access Builds available on jdk9.java.net/jigsaw In-Reply-To: References: <55F067A9.6070606@oracle.com> <55F1E85B.3040004@oracle.com> <55F1ED8E.3000904@oracle.com> Message-ID: <55F28888.60403@oracle.com> On 10/09/2015 22:21, Mani Sarkar wrote: > Hi Alan, > > Thanks for the detailed explanation and it would be great to find this > in your docs - I will link to it. > > The reasons I understood, jimage might go away, as I read this > https://bugs.*openjdk*.java.net/browse/JDK-8049369 > . > Yeah, it is confusing. That JBS issue tracked the creation of temporary image builder tool to use in JDK 9 until we had jlink. In jigsaw/jake then this image building tool has been removed and the build changed to create the run-time images with jlink. The Dependences section of JEP 261 has a few words on this. -Alan. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Alan.Bateman at oracle.com Mon Sep 14 17:49:10 2015 From: Alan.Bateman at oracle.com (Alan Bateman) Date: Mon, 14 Sep 2015 18:49:10 +0100 Subject: Project Jigsaw: Early-Access Builds available on jdk9.java.net/jigsaw In-Reply-To: References: <55F067A9.6070606@oracle.com> <55F1E85B.3040004@oracle.com> <55F1ED8E.3000904@oracle.com> <55F28888.60403@oracle.com> Message-ID: <55F70896.6020406@oracle.com> On 14/09/2015 17:48, Rahman USTA wrote: > |jlink --modulepath %JAVA_HOME%/jmods;mlib --addmods com.greetings --output greetingsapp| > After last step, greetingsapp folder generated with all Jigsaw > modules. How can I include just base mod or other compact mods ? > I assume what you are seeing is service binding with service providers and their dependencies getting linked into the image. Can you add "--limitmods com.greetings" to the command line and see if that gets you the run-time image that you expect? If you run "greetingsapp/bin/java -listmods" then it will list the names of the modules in the generated image. -Alan -------------- next part -------------- An HTML attachment was scrubbed... URL: From Alan.Bateman at oracle.com Tue Sep 15 13:09:38 2015 From: Alan.Bateman at oracle.com (Alan Bateman) Date: Tue, 15 Sep 2015 14:09:38 +0100 Subject: Project Jigsaw: Early-Access Builds available on jdk9.java.net/jigsaw In-Reply-To: References: <55F067A9.6070606@oracle.com> <55F1E85B.3040004@oracle.com> <55F1ED8E.3000904@oracle.com> <55F28888.60403@oracle.com> <55F70896.6020406@oracle.com> Message-ID: <55F81892.6090405@oracle.com> On 14/09/2015 20:11, Rahman USTA wrote: > Yes with "--limitmods com.greetings" the result as I expected. So, why > jlink links all modules without resolving over the root > "org.greetings" module? When jlink links all modules? > The -limitmods option is limiting the set of observable modules to com.greetings and its transitive dependences. Very useful for testing and also important when using the linker. There isn't a jlink JEP yet but I would expect the issue as to whether the tool does service binding by default or not be listed in its open options. In the current prototype then it always does service binding so this is why the resulting image has the service provider modules and their dependences. -Alan -------------- next part -------------- An HTML attachment was scrubbed... URL: From martinrb at google.com Thu Sep 17 00:18:51 2015 From: martinrb at google.com (Martin Buchholz) Date: Wed, 16 Sep 2015 17:18:51 -0700 Subject: stable subset of jtreg tests? Message-ID: Just now for the first time I ran all the jtreg tests in the "jdk_stable" test set using make test TEST=jdk_stable and I got around 50 failures out of 5000. Is that expected? Instead, I expect that with all the work on the test suite y'all have been doing, that the expected failure rate of something with a name like "jdk_stable" would be 0. -------------- next part -------------- An HTML attachment was scrubbed... URL: From jonathan.gibbons at oracle.com Thu Sep 17 00:21:33 2015 From: jonathan.gibbons at oracle.com (Jonathan Gibbons) Date: Wed, 16 Sep 2015 17:21:33 -0700 Subject: stable subset of jtreg tests? In-Reply-To: References: Message-ID: <55FA078D.3070802@oracle.com> On 09/16/2015 05:18 PM, Martin Buchholz wrote: > Just now for the first time I ran all the jtreg tests in the > "jdk_stable" test set using > make test TEST=jdk_stable > and I got around 50 failures out of 5000. > Is that expected? > > Instead, I expect that with all the work on the test suite y'all have > been doing, that the expected failure rate of something with a name > like "jdk_stable" would be 0. > Which forest? jdk9/dev? jigsaw/jake? -- Jon From joe.darcy at oracle.com Thu Sep 17 00:25:24 2015 From: joe.darcy at oracle.com (Joseph D. Darcy) Date: Wed, 16 Sep 2015 17:25:24 -0700 Subject: stable subset of jtreg tests? In-Reply-To: References: Message-ID: <55FA0874.3040900@oracle.com> Dropping the jtreg alias. On 9/16/2015 5:18 PM, Martin Buchholz wrote: > Just now for the first time I ran all the jtreg tests in the > "jdk_stable" test set using > make test TEST=jdk_stable > and I got around 50 failures out of 5000. > Is that expected? > > Instead, I expect that with all the work on the test suite y'all have > been doing, that the expected failure rate of something with a name > like "jdk_stable" would be 0. > For JDK 9 dev, the tier 1 tests across repos should be stable. Currently, only the langtools and jdk repos have non-empty tier 1 tests sets defined. If you run jtreg ... -exclude:ProblemList.txt -k:intermittent :tier1 there are some tier 1 test that are known to fail intermittently, but at this point with very low frequency (at least with the testing I'm exposed to). HTH, -Joe From joe.darcy at oracle.com Thu Sep 17 00:39:03 2015 From: joe.darcy at oracle.com (Joseph D. Darcy) Date: Wed, 16 Sep 2015 17:39:03 -0700 Subject: stable subset of jtreg tests? In-Reply-To: <55FA0874.3040900@oracle.com> References: <55FA0874.3040900@oracle.com> Message-ID: <55FA0BA7.2040707@oracle.com> PS For reference, see the tiered testing policy discussion for JDK 9 earlier this year: "Proposed new policies for JDK 9 regression tests: tiered testing, intermittent failures, and randomness," http://mail.openjdk.java.net/pipermail/jdk9-dev/2015-March/001991.html and the subsequent refinements and amendments: "Proposed new policies for JDK 9 regression tests: tiered testing, intermittent failures, and randomness," http://mail.openjdk.java.net/pipermail/jdk9-dev/2015-April/002164.html "Test policy follow-up, third testing tier," http://mail.openjdk.java.net/pipermail/jdk9-dev/2015-June/002325.html Implementing these polices has found and corrected a number of lingering test and product issues including: JDK-8022224: Rare bug in JISAutodetect charset detected by FindDecoderBugs test JDK-6854417: TESTBUG: java/util/regex/RegExTest.java fails intermittently Cheers, -Joe On 9/16/2015 5:25 PM, Joseph D. Darcy wrote: > Dropping the jtreg alias. > > On 9/16/2015 5:18 PM, Martin Buchholz wrote: >> Just now for the first time I ran all the jtreg tests in the >> "jdk_stable" test set using >> make test TEST=jdk_stable >> and I got around 50 failures out of 5000. >> Is that expected? >> >> Instead, I expect that with all the work on the test suite y'all have >> been doing, that the expected failure rate of something with a name >> like "jdk_stable" would be 0. >> > > For JDK 9 dev, the tier 1 tests across repos should be stable. > Currently, only the langtools and jdk repos have non-empty tier 1 > tests sets defined. > > If you run > > jtreg ... -exclude:ProblemList.txt -k:intermittent :tier1 > > there are some tier 1 test that are known to fail intermittently, but > at this point with very low frequency (at least with the testing I'm > exposed to). > > HTH, > > -Joe > From martinrb at google.com Thu Sep 17 01:02:39 2015 From: martinrb at google.com (Martin Buchholz) Date: Wed, 16 Sep 2015 18:02:39 -0700 Subject: stable subset of jtreg tests? In-Reply-To: <55FA078D.3070802@oracle.com> References: <55FA078D.3070802@oracle.com> Message-ID: On Wed, Sep 16, 2015 at 5:21 PM, Jonathan Gibbons < jonathan.gibbons at oracle.com> wrote: > > > On 09/16/2015 05:18 PM, Martin Buchholz wrote: > >> Just now for the first time I ran all the jtreg tests in the "jdk_stable" >> test set using >> make test TEST=jdk_stable >> and I got around 50 failures out of 5000. >> Is that expected? >> >> Instead, I expect that with all the work on the test suite y'all have >> been doing, that the expected failure rate of something with a name like >> "jdk_stable" would be 0. >> >> > Which forest? jdk9/dev? jigsaw/jake? > I saw this in both jdk9/jdk9 and jdk9/dev (but I wasn't trying to achieve a low-noise controlled environment) -------------- next part -------------- An HTML attachment was scrubbed... URL: From martinrb at google.com Thu Sep 17 01:17:51 2015 From: martinrb at google.com (Martin Buchholz) Date: Wed, 16 Sep 2015 18:17:51 -0700 Subject: stable subset of jtreg tests? In-Reply-To: <55FA0874.3040900@oracle.com> References: <55FA0874.3040900@oracle.com> Message-ID: Thanks Joe. I see those tier definitions in the various TEST.groups files but it's not obvious to me how to run them all with one simple invocation (neither make nor jtreg). The command line you gave doesn't seem to tell jtreg which TEST.ROOT directories to operate on. It looks like jtreg ... langtools/test:tier1 jdk/test:tier1 works, but I was looking for a simpler way to "run all the tier1 tests" without enumerating all the roots (there are currently 7!) On Wed, Sep 16, 2015 at 5:25 PM, Joseph D. Darcy wrote: > Dropping the jtreg alias. > > > On 9/16/2015 5:18 PM, Martin Buchholz wrote: > >> Just now for the first time I ran all the jtreg tests in the "jdk_stable" >> test set using >> make test TEST=jdk_stable >> and I got around 50 failures out of 5000. >> Is that expected? >> >> Instead, I expect that with all the work on the test suite y'all have >> been doing, that the expected failure rate of something with a name like >> "jdk_stable" would be 0. >> >> > For JDK 9 dev, the tier 1 tests across repos should be stable. Currently, > only the langtools and jdk repos have non-empty tier 1 tests sets defined. > > If you run > > jtreg ... -exclude:ProblemList.txt -k:intermittent :tier1 > > there are some tier 1 test that are known to fail intermittently, but at > this point with very low frequency (at least with the testing I'm exposed > to). > > HTH, > > -Joe > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From joe.darcy at oracle.com Thu Sep 17 01:32:54 2015 From: joe.darcy at oracle.com (Joseph D. Darcy) Date: Wed, 16 Sep 2015 18:32:54 -0700 Subject: stable subset of jtreg tests? In-Reply-To: References: <55FA0874.3040900@oracle.com> Message-ID: <55FA1846.6080009@oracle.com> Hi Martin, On 9/16/2015 6:17 PM, Martin Buchholz wrote: > Thanks Joe. > > I see those tier definitions in the various TEST.groups files but it's > not obvious to me how to run them all with one simple invocation > (neither make nor jtreg). Make support is coming, but not there yet: JDK-8075571: Support tiered testing make targets > > The command line you gave doesn't seem to tell jtreg which TEST.ROOT > directories to operate on. > > It looks like > jtreg ... langtools/test:tier1 jdk/test:tier1 > works, but I was looking for a simpler way to "run all the tier1 > tests" without enumerating all the roots (there are currently 7!) That is the simple(st) way currently. The jdk, langtools, nashorn, and jaxp repos currently use the tiered testing approach as defined in jtreg groups so you would "only" need four roots. The tier 2 tests are pretty stable too, but we certainly have instances were new repeatable failures are introduced, but we're getting better at addressing them quickly :-) -Joe > > > On Wed, Sep 16, 2015 at 5:25 PM, Joseph D. Darcy > wrote: > > Dropping the jtreg alias. > > > On 9/16/2015 5:18 PM, Martin Buchholz wrote: > > Just now for the first time I ran all the jtreg tests in the > "jdk_stable" test set using > make test TEST=jdk_stable > and I got around 50 failures out of 5000. > Is that expected? > > Instead, I expect that with all the work on the test suite > y'all have been doing, that the expected failure rate of > something with a name like "jdk_stable" would be 0. > > > For JDK 9 dev, the tier 1 tests across repos should be stable. > Currently, only the langtools and jdk repos have non-empty tier 1 > tests sets defined. > > If you run > > jtreg ... -exclude:ProblemList.txt -k:intermittent :tier1 > > there are some tier 1 test that are known to fail intermittently, > but at this point with very low frequency (at least with the > testing I'm exposed to). > > HTH, > > -Joe > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From martinrb at google.com Thu Sep 17 02:36:49 2015 From: martinrb at google.com (Martin Buchholz) Date: Wed, 16 Sep 2015 19:36:49 -0700 Subject: stable subset of jtreg tests? In-Reply-To: <55FA1846.6080009@oracle.com> References: <55FA0874.3040900@oracle.com> <55FA1846.6080009@oracle.com> Message-ID: OK, thanks, I managed to run my first tier test. What I (sometimes) really want is to apply a test filter to my test set: - those tests that are non-flaky and don't take "too many" resources to run You could harvest both of those qualities from your many quality engineering test runs. On Wed, Sep 16, 2015 at 6:32 PM, Joseph D. Darcy wrote: > Hi Martin, > > On 9/16/2015 6:17 PM, Martin Buchholz wrote: > > Thanks Joe. > > I see those tier definitions in the various TEST.groups files but it's not > obvious to me how to run them all with one simple invocation (neither make > nor jtreg). > > > Make support is coming, but not there yet: > > JDK-8075571: Support tiered testing make targets > > > The command line you gave doesn't seem to tell jtreg which TEST.ROOT > directories to operate on. > > It looks like > jtreg ... langtools/test:tier1 jdk/test:tier1 > works, but I was looking for a simpler way to "run all the tier1 tests" > without enumerating all the roots (there are currently 7!) > > > That is the simple(st) way currently. > > The jdk, langtools, nashorn, and jaxp repos currently use the tiered > testing approach as defined in jtreg groups so you would "only" need four > roots. > > The tier 2 tests are pretty stable too, but we certainly have instances > were new repeatable failures are introduced, but we're getting better at > addressing them quickly :-) > > -Joe > > > > On Wed, Sep 16, 2015 at 5:25 PM, Joseph D. Darcy > wrote: > >> Dropping the jtreg alias. >> >> >> On 9/16/2015 5:18 PM, Martin Buchholz wrote: >> >>> Just now for the first time I ran all the jtreg tests in the >>> "jdk_stable" test set using >>> make test TEST=jdk_stable >>> and I got around 50 failures out of 5000. >>> Is that expected? >>> >>> Instead, I expect that with all the work on the test suite y'all have >>> been doing, that the expected failure rate of something with a name like >>> "jdk_stable" would be 0. >>> >>> >> For JDK 9 dev, the tier 1 tests across repos should be stable. Currently, >> only the langtools and jdk repos have non-empty tier 1 tests sets defined. >> >> If you run >> >> jtreg ... -exclude:ProblemList.txt -k:intermittent :tier1 >> >> there are some tier 1 test that are known to fail intermittently, but at >> this point with very low frequency (at least with the testing I'm exposed >> to). >> >> HTH, >> >> -Joe >> >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From joe.darcy at oracle.com Thu Sep 17 14:39:10 2015 From: joe.darcy at oracle.com (joe darcy) Date: Thu, 17 Sep 2015 07:39:10 -0700 Subject: stable subset of jtreg tests? In-Reply-To: References: <55FA0874.3040900@oracle.com> <55FA1846.6080009@oracle.com> Message-ID: <55FAD08E.7090109@oracle.com> Hi Martin, On 9/16/2015 7:36 PM, Martin Buchholz wrote: > OK, thanks, I managed to run my first tier test. > > What I (sometimes) really want is to apply a test filter to my test set: > - those tests that are non-flaky and don't take "too many" resources > to run > You could harvest both of those qualities from your many quality > engineering test runs. FWIW, we see reasonable run times (20 minutes or less) on many platforms for running each of tier 1 and tier 2 tests if run on a well-sized server when using jtreg's agentvm mode and concurrency options. -Joe > > > On Wed, Sep 16, 2015 at 6:32 PM, Joseph D. Darcy > wrote: > > Hi Martin, > > On 9/16/2015 6:17 PM, Martin Buchholz wrote: >> Thanks Joe. >> >> I see those tier definitions in the various TEST.groups files but >> it's not obvious to me how to run them all with one simple >> invocation (neither make nor jtreg). > > Make support is coming, but not there yet: > > JDK-8075571: Support tiered testing make targets > >> >> The command line you gave doesn't seem to tell jtreg which >> TEST.ROOT directories to operate on. >> >> It looks like >> jtreg ... langtools/test:tier1 jdk/test:tier1 >> works, but I was looking for a simpler way to "run all the tier1 >> tests" without enumerating all the roots (there are currently 7!) > > That is the simple(st) way currently. > > The jdk, langtools, nashorn, and jaxp repos currently use the > tiered testing approach as defined in jtreg groups so you would > "only" need four roots. > > The tier 2 tests are pretty stable too, but we certainly have > instances were new repeatable failures are introduced, but we're > getting better at addressing them quickly :-) > > -Joe > >> >> >> On Wed, Sep 16, 2015 at 5:25 PM, Joseph D. Darcy >> > wrote: >> >> Dropping the jtreg alias. >> >> >> On 9/16/2015 5:18 PM, Martin Buchholz wrote: >> >> Just now for the first time I ran all the jtreg tests in >> the "jdk_stable" test set using >> make test TEST=jdk_stable >> and I got around 50 failures out of 5000. >> Is that expected? >> >> Instead, I expect that with all the work on the test >> suite y'all have been doing, that the expected failure >> rate of something with a name like "jdk_stable" would be 0. >> >> >> For JDK 9 dev, the tier 1 tests across repos should be >> stable. Currently, only the langtools and jdk repos have >> non-empty tier 1 tests sets defined. >> >> If you run >> >> jtreg ... -exclude:ProblemList.txt -k:intermittent :tier1 >> >> there are some tier 1 test that are known to fail >> intermittently, but at this point with very low frequency (at >> least with the testing I'm exposed to). >> >> HTH, >> >> -Joe >> >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From martijnverburg at gmail.com Sun Sep 27 13:03:01 2015 From: martijnverburg at gmail.com (Martijn Verburg) Date: Sun, 27 Sep 2015 14:03:01 +0100 Subject: Quality outreach: JOSM and OpenJDK adoption In-Reply-To: References: Message-ID: 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 sadhak001 at gmail.com Sun Sep 27 13:51:02 2015 From: sadhak001 at gmail.com (Mani Sarkar) Date: Sun, 27 Sep 2015 14:51:02 +0100 Subject: Quality outreach: JOSM and OpenJDK adoption In-Reply-To: References: Message-ID: Hi Vincent +1 - you are in Have you also tried building it against JDK Jigsaw - see https://jdk9.java.net/jigsaw In theory you should be fine if it already builds with jdk9. Cheers, Mani On Sun, Sep 27, 2015 at 2:03 PM, 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) > -- @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 rory.odonnell at oracle.com Mon Sep 28 09:25:30 2015 From: rory.odonnell at oracle.com (Rory O'Donnell) Date: Mon, 28 Sep 2015 10:25:30 +0100 Subject: Quality outreach: JOSM and OpenJDK adoption In-Reply-To: References: Message-ID: <5609078A.4090901@oracle.com> Hi Vincent, I will add your Project to the outreach wiki [7], I take it you will be the contact to list on the site ? What versions of the JDK are you testing against, would you like me to send you email when a new EA build is available ? The report [8] is created every 6 months , next report in Feb'2016 . Rgds,Rory On 27/09/2015 14:03, 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 jonathan.gibbons at oracle.com Mon Sep 28 18:43:46 2015 From: jonathan.gibbons at oracle.com (Jonathan Gibbons) Date: Mon, 28 Sep 2015 11:43:46 -0700 Subject: Quality outreach: JOSM and OpenJDK adoption In-Reply-To: References: Message-ID: <56098A62.1040601@oracle.com> 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: