September 2015 - quality-discuss

Re: Quality outreach: JOSM and OpenJDK adoption
by Martijn Verburg 05 Oct '15

05 Oct '15

Hi Vincent, I'd say that would be most welcome - Rory? On Sunday, 27 September 2015, Vincent Privat <vincent.privat(a)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/te… > [7] https://wiki.openjdk.java.net/display/quality/Quality+Outreach > [8] > > https://wiki.openjdk.java.net/display/quality/Quality+Outreach+report+Sept+… > -- Cheers, Martijn (Sent from Gmail Mobile)

5 6

stable subset of jtreg tests?
by Martin Buchholz 17 Sep '15

17 Sep '15

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.

4 8

Re: Project Jigsaw: Early-Access Builds available on jdk9.java.net/jigsaw
by Alan Bateman 15 Sep '15

15 Sep '15

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

1 0

Re: Project Jigsaw: Early-Access Builds available on jdk9.java.net/jigsaw
by Alan Bateman 14 Sep '15

14 Sep '15

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

1 0

Re: Project Jigsaw: Early-Access Builds available on jdk9.java.net/jigsaw
by Mani Sarkar 11 Sep '15

11 Sep '15

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 <james.connors(a)oracle.com> 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 <http://twitter.com/theNeomatrix369>* | **Blog <http://neomatrix369.wordpress.com>** | *LJC Associate & LJC Advocate (@adoptopenjdk & @adoptajsr programs) *Meet-a-Project - *MutabilityDetector <https://github.com/MutabilityDetector>* | **Bitbucket <https://bitbucket.org/neomatrix369>* * | **Github <https://github.com/neomatrix369>* * | **LinkedIn <http://uk.linkedin.com/pub/mani-sarkar/71/a77/39b>* *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!*

2 1

Project Jigsaw: Early-Access Builds available on jdk9.java.net/jigsaw
by Rory O'Donnell 10 Sep '15

10 Sep '15

Hi All, Early-access builds of JDK 9 with Project Jigsaw are available for download at jdk9.java.net/jigsaw <http://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 <http://openjdk.java.net/projects/jigsaw/quick-start>, 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 <mailto:jpms-spec-comments@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.h… -- Rgds,Rory O'Donnell Quality Engineering Manager Oracle EMEA , Dublin, Ireland

3 3

Quality Outreach Update
by Rory O'Donnell 02 Sep '15

02 Sep '15

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 <https://wiki.openjdk.java.net/display/quality/Quality+Outreach> 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 <https://wiki.openjdk.java.net/display/quality/Quality+Outreach> page in the coming days. Rgds, Rory -- Rgds,Rory O'Donnell Quality Engineering Manager Oracle EMEA , Dublin, Ireland

1 1