We have some Code Coverage results from JCov/JTreg!

[Mani Sarkar]

On advice from our lead devops, we have decided to move the whole
testoutput folder to another location so during builds the reports from
previous builds are still available, the link to the new location to the
jcov reports is:

https://adopt-openjdk.ci.cloudbees.com/view/OpenJDK/job/openjdk-1.9-linux-x86_64/ws/testoutput/jdk_core/JTreport/jcov/index.html

The reports are archived and available for every build as tar.gz files. I
also have a separate archive for just jcov created along with the two
available archives under latest builds.

Cheers,
Mani

On Thu, Jan 29, 2015 at 9:46 PM, Mani Sarkar <sadhak001 at gmail.com> wrote:

> Great to have these coverage metrics after a long time - thanks to John
> Oliver for the team work we did to get this off the ground, mostly it was
> his expertise to do the necessary tweaks.
>
> Please save this link as it will automatically be updated with regular
> commits made into the jdk9/dev repo.
>
> Any feedback or queries, feel free to get back to us.
>
> Cheers,
> Mani
>
> On Thu, Jan 29, 2015 at 3:39 PM, Martijn Verburg <martijnverburg at gmail.com
> > wrote:
>
>> Thanks Jonathan,
>>
>> For everyone else, we have our first published results for jdk9 which will
>> be built nightly! See the following link as an example:
>>
>>
>> https://adopt-openjdk.ci.cloudbees.com/job/openjdk-1.9-linux-x86_64/ws/build/linux-x86_64-normal-server-release/testoutput/jdk_core/JTreport/jcov/index.html
>>
>> The numbers for JDK Core are better than expected (around 70%)
>>
>> Kudos to John Oliver and Mani Sarkar for getting the Cloudbees Jenkins
>> build into place.
>>
>> We can discuss what this all means and what could be hosted / linked to
>> from where, but it's a good start!
>>
>>
>> Cheers,
>> Martijn
>>
>> On 29 January 2015 at 03:20, Jonathan Gibbons <
>> jonathan.gibbons at oracle.com>
>> wrote:
>>
>> >
>> > On 01/28/2015 06:51 PM, Jonathan Gibbons wrote:
>> >
>> >>
>> >> On 01/25/2015 06:45 AM, Martijn Verburg wrote:
>> >>
>> >>> Also, I'm not sure if we should reach out to code-tools, jdk9-dev and
>> >>> jdk8u-dev and ask them to have links to the CI farm as well?  I think
>> it
>> >>> would be a good idea to highlight this though.
>> >>>
>> >>> Cheers,
>> >>> Martijn
>> >>>
>> >>
>> >> Consider the code-tools group reached. The jtreg page has had a link
>> for
>> >> a while, but I'll make a more general link on the Code Tools page as
>> well.
>> >>
>> >> -- Jon
>> >>
>> >>
>> > Done.
>> >
>> > http://openjdk.java.net/projects/code-tools/
>> > See "Other Resources". (It may take a few minutes to show up.)
>> >
>> > -- Jon
>> >
>>
>
>
>
> --
> @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 2015:* http://www.devoxx.co.uk/
>
> *Don't chase success, rather aim for "Excellence", and success will come
> chasing after you!*
>



-- 
@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 2015:* 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: <http://mail.openjdk.java.net/pipermail/quality-discuss/attachments/20150130/e367a5d7/attachment-0001.html>