We have some Code Coverage results from JCov/JTreg!
Rory O'Donnell
rory.odonnell at oracle.com
Mon Jan 19 17:33:01 UTC 2015
On 19/01/2015 17:28, Martijn Verburg wrote:
> Hi Rory,
>
> Understood - it will be good to be able to encourage various OpenJDK
> members to contribute / port tests into it and measure that. Small
> steps :-).
Sounds good Martijn, talk more on this at FOSDEM ?
Rgds,Rory
>
> On 19 January 2015 at 16:35, Rory O'Donnell <rory.odonnell at oracle.com
> <mailto:rory.odonnell at oracle.com>> wrote:
>
>
> On 19/01/2015 15:36, Martijn Verburg wrote:
>> Hi Rory,
>>
>> Thanks - we're looking into the existing Cloudbees Jenkins
>> instance to do this.
> ok
>> A second question quick question - do the numbers we're
>> publishing look right compared to your internal ones?
>> Appreciate non OpenJDK tests run by Oracle means that they cover
>> more.
>>
> Comparing our internal numbers with yours would be like comparing
> apples with pears
> I'm afraid.
>
> Rgds,Rory
>
>> Cheers,
>> Martijn
>>
>> On 19 January 2015 at 15:18, Rory O'Donnell
>> <rory.odonnell at oracle.com <mailto:rory.odonnell at oracle.com>> wrote:
>>
>>
>> On 19/01/2015 10:55, Martijn Verburg wrote:
>>
>> Hi all,
>>
>> John Oliver and Mani Sarkar spent some time on the most
>> recent Adopt OpenJDK hackday and managed to get what
>> looks like to be meaningful code coverage numbers for
>> OpenJDK using the jcov/jtreg tools:
>>
>> Results for jdk9: http://sticky.uwcs.co.uk/jcov/
>>
>> ========Code Tools Dev========
>>
>> The configuration John used was as follows (is this the
>> correct usage pattern?):
>>
>> Build jdk images
>> install jtreg with the jcov
>>
>> export the normal vars:
>>
>> ```
>> export SOURCE_CODE=/home/joliver/workspace/jdk9/
>> export JTREG_INSTALL=/home/joliver/workspace/jtreg
>> export JT_HOME=$JTREG_INSTALL
>> export JTREG_HOME=$JTREG_INSTALL
>> export
>> PRODUCT_HOME=$SOURCE_CODE/build/linux-x86_64-normal-server-release/images/jdk
>>
>> export JPRT_JTREG_HOME=${JT_HOME}
>> export JPRT_JAVA_HOME=${PRODUCT_HOME}
>> export JTREG_TIMEOUT_FACTOR=5
>> export CONCURRENCY=8
>> ```
>>
>> cd into jdk/test
>>
>> edit the Makefile and add the following:
>>
>> ```
>> jdkroot=/home/joliver/workspace/jdk9/
>>
>> JTREG_TEST_OPTIONS +=
>> -jcov/classes:$(jdkroot)/build/linux-x86_64-normal-server-release/jdk/modules/java.base
>> JTREG_TEST_OPTIONS +=
>> -jcov/source:$(jdkroot)/jdk/src/java.base/share/classes
>> JTREG_TEST_OPTIONS += -jcov/include:*
>> ```
>>
>> just before the line: # Make sure jtreg exists
>>
>> then just run "make test" inside the root
>>
>> =======Quality Discuss=======
>>
>> Hi Martijn,
>>
>> Posting the results on our wiki won't work, so I can provide
>> a link to the
>> results. Let me know when you have decided on the link
>> locations.
>>
>> Rgds,Rory
>>
>>
>> Is this something that could be hosted by the quality
>> group for the major OpenJDK code lines (7u, 8u and jdk9)?
>>
>> If not then the Adoption Group can host it on one of
>> their external servers temporarily and we could link to
>> that from the wiki(s)/project page(s).
>>
>> Cheers,
>> Martijn
>>
>>
>> --
>> Rgds,Rory O'Donnell
>> Quality Engineering Manager
>> Oracle EMEA , Dublin, Ireland
>>
>>
>
> --
> Rgds,Rory O'Donnell
> Quality Engineering Manager
> Oracle EMEA , Dublin, Ireland
>
>
--
Rgds,Rory O'Donnell
Quality Engineering Manager
Oracle EMEA , Dublin, Ireland
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.openjdk.java.net/pipermail/quality-discuss/attachments/20150119/137bdebe/attachment.html>
More information about the quality-discuss
mailing list