Re: JDK 9 build 151 test results now available

[Volker Simonis]

Hi Muneer,

thanks for updating the pages. Their content seems right now.

Unfortunately all the build results pages:

http://download.java.net/openjdk/testresults/8
http://download.java.net/openjdk/testresults/9
http://download.java.net/openjdk/testresults/10

redirect to pages which have broken "How to run these tests?" links.
They all point to
http://download.java.net/openjdk/testresults/docs/howtoruntests.html
which can not be found. Actually all the links on these pages (e.g.
the various archive links) on these pages are broken as well!

Strangely, the following links

http://download.java.net/openjdk/testresults/8/index.html
http://download.java.net/openjdk/testresults/9/index.html
http://download.java.net/openjdk/testresults/10/index.html

show slightly different looking pages with the same content but with
correct "How to run these tests?" links:

http://download.java.net/openjdk/testresults/8/docs/howtoruntests.html
http://download.java.net/openjdk/testresults/9/docs/howtoruntests.html
http://download.java.net/openjdk/testresults/10/docs/howtoruntests.html

The other links are also correct.

Can you please fix this as well and let the more generix URLs (i.e.
testresults/8, testresults/9, testresults/10) point to the correct
pages. Otherwise  this is quite confusing (it actually took me quite
some time to find it out :)

Thank you and best regards,
Volker

On Fri, Jan 12, 2018 at 12:36 PM, Muneer Kolarkunnu
<abdul.kolarku...@oracle.com> wrote:
> Hi Volker,
>
> I will incorporate your comments along with JDK10 build39 test results.
> Thanks for your review and suggestions.
>
> Regards,
> Muneer
>
> -Original Message-
> From: Volker Simonis [mailto:volker.simo...@gmail.com]
> Sent: Thursday, January 11, 2018 8:49 PM
> To: Muneer Kolarkunnu <abdul.kolarku...@oracle.com>
> Cc: quality-discuss@openjdk.java.net; Rory O'Donnell 
> <rory.odonn...@oracle.com>; Dalibor Topic <dalibor.to...@oracle.com>
> Subject: Re: JDK 9 build 151 test results now available
>
> On Mon, Nov 27, 2017 at 10:54 AM, Muneer Kolarkunnu 
> <abdul.kolarku...@oracle.com> wrote:
>> Hi Volker,
>>
>> Thanks for the feedback.
>> I updated the page 'howtoruntests' to conform to the latest consolidated 
>> repository.
>
> Hi Muneer, Dalibor, Rory,
>
> I see that the 'howtoruntests' has been updated at 
> http://download.java.net/openjdk/testresults/10/docs/howtoruntests.html
> but unfortunately it is still not accurate.
>
> In section "2.3 Running tests in test/hotspot" the command line should read:
>
> $ jtreg -dir:{openjdk source top directory}/test/hotspot/jtreg 
> -verbose:summary -nativepath:{location of the hotspot test native library} 
> -exclude:{openjdk source top directory}/test/hotspot/jtreg/ProblemList.txt 
> -conc:auto -a -ignore:quiet -timeoutFactor:5 -agentvm -testjdk:{location of 
> the test jdk} :hotspot_all_no_apps
>
> (i.e. the arguments for '-dir' and '-exclude' require "test/hotspot/jtreg" 
> instead of "test/hotspot/jtreg")
>
> I'd also like to suggest to add the following extra explanation as footnotes 
> to the sections 2.1 and 2.3:
>
> 2.1 Running tests in test/jdk
> $ jtreg -dir:{openjdk source top directory}/test/jdk -verbose:summary 
> -nativepath:{location of the jdk test native library} -exclude:{openjdk 
> source top directory}/test/jdk/ProblemList.txt
> -conc:2 -Xmx512m -a -ignore:quiet -timeoutFactor:5 -agentvm 
> -testjdk:{location of the test jdk} :jdk_stable
>
> {location of the jdk test native library}: has to be generated at build time 
> of the test jdk by invoking "make test-image". Located in the build directory 
> under "images/test/jdk/jtreg/native/"
>
> 2.3 Running tests in test/hotspot
> $ jtreg -dir:{openjdk source top directory}/test/hotspot/jtreg 
> -verbose:summary -nativepath:{location of the hotspot test native library} 
> -exclude:{openjdk source top directory}/test/hotspot/jtreg/ProblemList.txt 
> -conc:auto -a -ignore:quiet -timeoutFactor:5 -agentvm -testjdk:{location of 
> the test jdk} :hotspot_all_no_apps
>
> {location of the hotspot test native library}: has to be generated at build 
> time of the test jdk by invoking "make test-image". Located in the build 
> directory under "images/test/hotspot/jtreg/native/"
>
> Without a properly specified "-nativepath" a lot of tests will fail and most 
> people probably won't know why.
>
> Regards,
> Volker
>
>> Muneer
>>
>> -Original Message-
>> From: Volker Simonis [mailto:volker.simo...@gmail.com]
>> Sent: Thursday, November 23, 2017 1:40 PM
>> To: Martijn Verburg
>> Cc: quality-discuss@openjdk.java.net
>> Subject: Re: JDK

RE: JDK 9 build 151 test results now available

[Muneer Kolarkunnu]

Hi Volker,

I will incorporate your comments along with JDK10 build39 test results.
Thanks for your review and suggestions.

Regards,
Muneer

-Original Message-
From: Volker Simonis [mailto:volker.simo...@gmail.com] 
Sent: Thursday, January 11, 2018 8:49 PM
To: Muneer Kolarkunnu <abdul.kolarku...@oracle.com>
Cc: quality-discuss@openjdk.java.net; Rory O'Donnell 
<rory.odonn...@oracle.com>; Dalibor Topic <dalibor.to...@oracle.com>
Subject: Re: JDK 9 build 151 test results now available

On Mon, Nov 27, 2017 at 10:54 AM, Muneer Kolarkunnu 
<abdul.kolarku...@oracle.com> wrote:
> Hi Volker,
>
> Thanks for the feedback.
> I updated the page 'howtoruntests' to conform to the latest consolidated 
> repository.

Hi Muneer, Dalibor, Rory,

I see that the 'howtoruntests' has been updated at 
http://download.java.net/openjdk/testresults/10/docs/howtoruntests.html
but unfortunately it is still not accurate.

In section "2.3 Running tests in test/hotspot" the command line should read:

$ jtreg -dir:{openjdk source top directory}/test/hotspot/jtreg -verbose:summary 
-nativepath:{location of the hotspot test native library} -exclude:{openjdk 
source top directory}/test/hotspot/jtreg/ProblemList.txt -conc:auto -a 
-ignore:quiet -timeoutFactor:5 -agentvm -testjdk:{location of the test jdk} 
:hotspot_all_no_apps

(i.e. the arguments for '-dir' and '-exclude' require "test/hotspot/jtreg" 
instead of "test/hotspot/jtreg")

I'd also like to suggest to add the following extra explanation as footnotes to 
the sections 2.1 and 2.3:

2.1 Running tests in test/jdk
$ jtreg -dir:{openjdk source top directory}/test/jdk -verbose:summary 
-nativepath:{location of the jdk test native library} -exclude:{openjdk source 
top directory}/test/jdk/ProblemList.txt
-conc:2 -Xmx512m -a -ignore:quiet -timeoutFactor:5 -agentvm -testjdk:{location 
of the test jdk} :jdk_stable

{location of the jdk test native library}: has to be generated at build time of 
the test jdk by invoking "make test-image". Located in the build directory 
under "images/test/jdk/jtreg/native/"

2.3 Running tests in test/hotspot
$ jtreg -dir:{openjdk source top directory}/test/hotspot/jtreg -verbose:summary 
-nativepath:{location of the hotspot test native library} -exclude:{openjdk 
source top directory}/test/hotspot/jtreg/ProblemList.txt -conc:auto -a 
-ignore:quiet -timeoutFactor:5 -agentvm -testjdk:{location of the test jdk} 
:hotspot_all_no_apps

{location of the hotspot test native library}: has to be generated at build 
time of the test jdk by invoking "make test-image". Located in the build 
directory under "images/test/hotspot/jtreg/native/"

Without a properly specified "-nativepath" a lot of tests will fail and most 
people probably won't know why.

Regards,
Volker

> Muneer
>
> -Original Message-
> From: Volker Simonis [mailto:volker.simo...@gmail.com]
> Sent: Thursday, November 23, 2017 1:40 PM
> To: Martijn Verburg
> Cc: quality-discuss@openjdk.java.net
> Subject: Re: JDK 9 build 151 test results now available
>
> Hi Dalibor,
>
> could you please update:
>
> http://download.java.net/openjdk/testresults/10/docs/howtoruntests.htm
> l
>
> to conform to the latest, consolidated repository. The description still 
> refers to the various sub-repos (jdk/test, hotspot/test, etc..) which are 
> gone now.
>
> Thank you and best regards,
> Volker
>
>
> On Wed, Nov 22, 2017 at 9:44 PM, Martijn Verburg <martijnverb...@gmail.com> 
> wrote:
>> Hi Dalibor,
>>
>> That's a really good idea.  Any objections to having an automated 
>> system sign up to this mailing list and posting on a regular schedule?
>>
>> Cheers,
>> Martijn
>>
>> On 22 November 2017 at 13:35, dalibor topic 
>> <dalibor.to...@oracle.com>
>> wrote:
>>>
>>> Thanks, Martijn - the relevant link for the test results is at 
>>> https://ci.adoptopenjdk.net/view/OpenJDK%20tests/ .
>>>
>>> It'd be nice if someone from LJC or IBM would post a link/summary of 
>>> the test results regularly to this list as well.
>>>
>>> cheers,
>>> dalibor topic
>>>
>>> On 21.11.2017 22:01, Martijn Verburg wrote:
>>>>
>>>> To complete this old thread,
>>>>
>>>> We now have a build farm at https://ci.adoptpenjdk.net with a 
>>>> corresponding website at https://www.adoptopenjdk.net and all of 
>>>> the supporting repos at https://www.github.com/adoptopenjdk
>>>>
>>>> If you'd like to join the community Slack or GitHub and get a 
>>>> walkthrough, please let me know!
>>>>
>>>> Cheers,
>>>> Martijn
>

Re: JDK 9 build 151 test results now available

[Rory O'Donnell]

On 23/11/2017 09:23, dalibor topic wrote:



On 22.11.2017 21:44, Martijn Verburg wrote:

Hi Dalibor,

That's a really good idea.  Any objections to having an automated 
system sign up to this mailing list and posting on a regular schedule?


No objections from me, as long as it is configured to send mail for 
tagged builds (as Oracle does for early access builds on Oracle 
Linux), rather than on each commit, or some other more frequent 
schedule. I.e. once a week is fine, as it allows and encourages 
comparison between different builds & platforms, multiple times per 
day is probably too noisy.


Rory?

Agreed, once a week seems like a good interval .

Rgds,Rory


cheers,
dalibor topic



Cheers,
Martijn

On 22 November 2017 at 13:35, dalibor topic > wrote:


    Thanks, Martijn - the relevant link for the test results is at
    https://ci.adoptopenjdk.net/view/OpenJDK%20tests/
     .

    It'd be nice if someone from LJC or IBM would post a link/summary of
    the test results regularly to this list as well.

    cheers,
    dalibor topic

    On 21.11.2017 22:01, Martijn Verburg wrote:

    To complete this old thread,

    We now have a build farm at https://ci.adoptpenjdk.net with a
    corresponding website at https://www.adoptopenjdk.net and all of
    the supporting repos at https://www.github.com/adoptopenjdk
    

    If you'd like to join the community Slack or GitHub and get a
    walkthrough, please let me know!

    Cheers,
    Martijn

    On 19 January 2017 at 22:12, Martijn Verburg
    
    >> wrote:

     Hi all,

     I'm partly on holiday this week but will get back to all of
    you with
     the straw man we had come up with a few FOSDEM's ago on how
    we could
     tackle this

     Cheers,
     Martijn

     On 17 January 2017 at 21:49, Jonathan Gibbons
     
    >>
     wrote:

         If someone can collect the different sets of jtreg 
output,

         there's a related utility called "jtdiff" that can be
    used to
         generate combined reports.  It can compare either 
full work

         directories, or the report/text/summary.txt files. The
    latter
         may be sufficient in this case.

         -- Jon



         On 1/16/17 3:54 AM, Stuart Monteith wrote:

             Hello,
                      I'm Stuart Monteith in Linaro, working on
    OpenJDK
             on ARM's 64-bit
             Aarch64 platform. We currently publish aarch64 
testing

             results to the
             aarch64-port-dev mailing list and host results on
    http://openjdk.linaro.org/ . What I would find useful would
             be a means
             to collate results across all the platforms, with
    perhaps a
             method to
             collate results from separate build farms. I'm sure
    a common
             set formats
             for presentation could be agreed upon. Knowing that
    a change
             in, say,
             x86, breaks arm, aarch64, ppc64, s390x would be
    useful for
             everyone.

             Best regards,
                  Stuart


             On 15/01/17 13:07, Martijn Verburg wrote:

                 Hi all,

                 The LJC has plans to do this with a small build
    farm for
                 some of the
                 more common platforms.  This will be for R 
and

                 academic research
                 purposes only.

                 If you have OpenJDK / Jenkins build experience
    and would
                 like to help
                 then please let me know!

                 Cheers,
                 Martijn

                 On 13 January 2017 at 20:50, dalibor topic
                 
    >

                 
                 

Re: JDK 9 build 151 test results now available

[dalibor topic]

On 22.11.2017 21:44, Martijn Verburg wrote:

Hi Dalibor,

That's a really good idea.  Any objections to having an automated system 
sign up to this mailing list and posting on a regular schedule?


No objections from me, as long as it is configured to send mail for 
tagged builds (as Oracle does for early access builds on Oracle Linux), 
rather than on each commit, or some other more frequent schedule. I.e. 
once a week is fine, as it allows and encourages comparison between 
different builds & platforms, multiple times per day is probably too noisy.


Rory?

cheers,
dalibor topic



Cheers,
Martijn

On 22 November 2017 at 13:35, dalibor topic > wrote:


Thanks, Martijn - the relevant link for the test results is at
https://ci.adoptopenjdk.net/view/OpenJDK%20tests/
 .

It'd be nice if someone from LJC or IBM would post a link/summary of
the test results regularly to this list as well.

cheers,
dalibor topic

On 21.11.2017 22:01, Martijn Verburg wrote:

To complete this old thread,

We now have a build farm at https://ci.adoptpenjdk.net with a
corresponding website at https://www.adoptopenjdk.net and all of
the supporting repos at https://www.github.com/adoptopenjdk


If you'd like to join the community Slack or GitHub and get a
walkthrough, please let me know!

Cheers,
Martijn

On 19 January 2017 at 22:12, Martijn Verburg

>> wrote:

     Hi all,

     I'm partly on holiday this week but will get back to all of
you with
     the straw man we had come up with a few FOSDEM's ago on how
we could
     tackle this

     Cheers,
     Martijn

     On 17 January 2017 at 21:49, Jonathan Gibbons
     
>>
     wrote:

         If someone can collect the different sets of jtreg output,
         there's a related utility called "jtdiff" that can be
used to
         generate combined reports.  It can compare either full work
         directories, or the report/text/summary.txt files. The
latter
         may be sufficient in this case.

         -- Jon



         On 1/16/17 3:54 AM, Stuart Monteith wrote:

             Hello,
                      I'm Stuart Monteith in Linaro, working on
OpenJDK
             on ARM's 64-bit
             Aarch64 platform. We currently publish aarch64 testing
             results to the
             aarch64-port-dev mailing list and host results on
http://openjdk.linaro.org/ . What I would find useful would
             be a means
             to collate results across all the platforms, with
perhaps a
             method to
             collate results from separate build farms. I'm sure
a common
             set formats
             for presentation could be agreed upon. Knowing that
a change
             in, say,
             x86, breaks arm, aarch64, ppc64, s390x would be
useful for
             everyone.

             Best regards,
                  Stuart


             On 15/01/17 13:07, Martijn Verburg wrote:

                 Hi all,

                 The LJC has plans to do this with a small build
farm for
                 some of the
                 more common platforms.  This will be for R and
                 academic research
                 purposes only.

                 If you have OpenJDK / Jenkins build experience
and would
                 like to help
                 then please let me know!

                 Cheers,
                 Martijn

                 On 13 January 2017 at 20:50, dalibor topic
                 
>
                 
                 

Re: JDK 9 build 151 test results now available

[Rory O'Donnell]

Volker,

We added Note 3 to http://download.java.net/openjdk/testresults/10/

earlier this week, we should have updated the "howto" also, will get 
that done shortly.


We are still evaluating the most suitable hotspot test group(s), bear 
with us while we get this sorted.



Rgds,Rory


On 23/11/2017 08:10, Volker Simonis wrote:

Hi Dalibor,

could you please update:

http://download.java.net/openjdk/testresults/10/docs/howtoruntests.html

to conform to the latest, consolidated repository. The description
still refers to the various sub-repos (jdk/test, hotspot/test, etc..)
which are gone now.

Thank you and best regards,
Volker


On Wed, Nov 22, 2017 at 9:44 PM, Martijn Verburg
 wrote:

Hi Dalibor,

That's a really good idea.  Any objections to having an automated system
sign up to this mailing list and posting on a regular schedule?

Cheers,
Martijn

On 22 November 2017 at 13:35, dalibor topic 
wrote:

Thanks, Martijn - the relevant link for the test results is at
https://ci.adoptopenjdk.net/view/OpenJDK%20tests/ .

It'd be nice if someone from LJC or IBM would post a link/summary of the
test results regularly to this list as well.

cheers,
dalibor topic

On 21.11.2017 22:01, Martijn Verburg wrote:

To complete this old thread,

We now have a build farm at https://ci.adoptpenjdk.net with a
corresponding website at https://www.adoptopenjdk.net and all of the
supporting repos at https://www.github.com/adoptopenjdk

If you'd like to join the community Slack or GitHub and get a
walkthrough, please let me know!

Cheers,
Martijn

On 19 January 2017 at 22:12, Martijn Verburg > wrote:

 Hi all,

 I'm partly on holiday this week but will get back to all of you with
 the straw man we had come up with a few FOSDEM's ago on how we could
 tackle this

 Cheers,
 Martijn

 On 17 January 2017 at 21:49, Jonathan Gibbons
 >
 wrote:

 If someone can collect the different sets of jtreg output,
 there's a related utility called "jtdiff" that can be used to
 generate combined reports.  It can compare either full work
 directories, or the report/text/summary.txt files. The latter
 may be sufficient in this case.

 -- Jon



 On 1/16/17 3:54 AM, Stuart Monteith wrote:

 Hello,
  I'm Stuart Monteith in Linaro, working on OpenJDK
 on ARM's 64-bit
 Aarch64 platform. We currently publish aarch64 testing
 results to the
 aarch64-port-dev mailing list and host results on
 http://openjdk.linaro.org/ . What I would find useful would
 be a means
 to collate results across all the platforms, with perhaps a
 method to
 collate results from separate build farms. I'm sure a common
 set formats
 for presentation could be agreed upon. Knowing that a change
 in, say,
 x86, breaks arm, aarch64, ppc64, s390x would be useful for
 everyone.

 Best regards,
  Stuart


 On 15/01/17 13:07, Martijn Verburg wrote:

 Hi all,

 The LJC has plans to do this with a small build farm for
 some of the
 more common platforms.  This will be for R and
 academic research
 purposes only.

 If you have OpenJDK / Jenkins build experience and would
 like to help
 then please let me know!

 Cheers,
 Martijn

 On 13 January 2017 at 20:50, dalibor topic
 
 >> wrote:

   On 12.01.2017 20:51, Martin Buchholz wrote:

   Oracle runs tests on many platforms; why does
 this report only
   include
   one platform?


   It would be rather nice to see more people run the
 OpenJDK jtreg
   tests on their own OpenJDK builds on platforms of
 their choice and
   post the results regularly.

   The great thing about these tests is that it
 doesn't have to be
   someone at Oracle doing all the running and all
 the posting.

   cheers,
   dalibor topic
   --
    Dalibor Topic | Principal
 Product Manager
   Phone: 

Re: JDK 9 build 151 test results now available

[Martijn Verburg]

Hi Dalibor,

That's a really good idea.  Any objections to having an automated system
sign up to this mailing list and posting on a regular schedule?

Cheers,
Martijn

On 22 November 2017 at 13:35, dalibor topic 
wrote:

> Thanks, Martijn - the relevant link for the test results is at
> https://ci.adoptopenjdk.net/view/OpenJDK%20tests/ .
>
> It'd be nice if someone from LJC or IBM would post a link/summary of the
> test results regularly to this list as well.
>
> cheers,
> dalibor topic
>
> On 21.11.2017 22:01, Martijn Verburg wrote:
>
>> To complete this old thread,
>>
>> We now have a build farm at https://ci.adoptpenjdk.net with a
>> corresponding website at https://www.adoptopenjdk.net and all of the
>> supporting repos at https://www.github.com/adoptopenjdk
>>
>> If you'd like to join the community Slack or GitHub and get a
>> walkthrough, please let me know!
>>
>> Cheers,
>> Martijn
>>
>> On 19 January 2017 at 22:12, Martijn Verburg > > wrote:
>>
>> Hi all,
>>
>> I'm partly on holiday this week but will get back to all of you with
>> the straw man we had come up with a few FOSDEM's ago on how we could
>> tackle this
>>
>> Cheers,
>> Martijn
>>
>> On 17 January 2017 at 21:49, Jonathan Gibbons
>> >
>> wrote:
>>
>> If someone can collect the different sets of jtreg output,
>> there's a related utility called "jtdiff" that can be used to
>> generate combined reports.  It can compare either full work
>> directories, or the report/text/summary.txt files. The latter
>> may be sufficient in this case.
>>
>> -- Jon
>>
>>
>>
>> On 1/16/17 3:54 AM, Stuart Monteith wrote:
>>
>> Hello,
>>  I'm Stuart Monteith in Linaro, working on OpenJDK
>> on ARM's 64-bit
>> Aarch64 platform. We currently publish aarch64 testing
>> results to the
>> aarch64-port-dev mailing list and host results on
>> http://openjdk.linaro.org/ . What I would find useful would
>> be a means
>> to collate results across all the platforms, with perhaps a
>> method to
>> collate results from separate build farms. I'm sure a common
>> set formats
>> for presentation could be agreed upon. Knowing that a change
>> in, say,
>> x86, breaks arm, aarch64, ppc64, s390x would be useful for
>> everyone.
>>
>> Best regards,
>>  Stuart
>>
>>
>> On 15/01/17 13:07, Martijn Verburg wrote:
>>
>> Hi all,
>>
>> The LJC has plans to do this with a small build farm for
>> some of the
>> more common platforms.  This will be for R and
>> academic research
>> purposes only.
>>
>> If you have OpenJDK / Jenkins build experience and would
>> like to help
>> then please let me know!
>>
>> Cheers,
>> Martijn
>>
>> On 13 January 2017 at 20:50, dalibor topic
>> > om>
>> > >> wrote:
>>
>>   On 12.01.2017 20:51, Martin Buchholz wrote:
>>
>>   Oracle runs tests on many platforms; why does
>> this report only
>>   include
>>   one platform?
>>
>>
>>   It would be rather nice to see more people run the
>> OpenJDK jtreg
>>   tests on their own OpenJDK builds on platforms of
>> their choice and
>>   post the results regularly.
>>
>>   The great thing about these tests is that it
>> doesn't have to be
>>   someone at Oracle doing all the running and all
>> the posting.
>>
>>   cheers,
>>   dalibor topic
>>   --
>>    Dalibor Topic | Principal
>> Product Manager
>>   Phone: +494089091214 
>>  > 
>>   > | Mobile: +491737185961
>>  
>>   
>> >
>>
>>   ORACLE Deutschland B.V. & Co. KG | Kühnehöfe 5 |
>> 22761 

Re: JDK 9 build 151 test results now available

[Martijn Verburg]

Hi all,

I'm partly on holiday this week but will get back to all of you with the
straw man we had come up with a few FOSDEM's ago on how we could tackle this

Cheers,
Martijn

On 17 January 2017 at 21:49, Jonathan Gibbons 
wrote:

> If someone can collect the different sets of jtreg output, there's a
> related utility called "jtdiff" that can be used to generate combined
> reports.  It can compare either full work directories, or the
> report/text/summary.txt files. The latter may be sufficient in this case.
>
> -- Jon
>
>
>
> On 1/16/17 3:54 AM, Stuart Monteith wrote:
>
>> Hello,
>> I'm Stuart Monteith in Linaro, working on OpenJDK on ARM's 64-bit
>> Aarch64 platform. We currently publish aarch64 testing results to the
>> aarch64-port-dev mailing list and host results on
>> http://openjdk.linaro.org/ . What I would find useful would be a means
>> to collate results across all the platforms, with perhaps a method to
>> collate results from separate build farms. I'm sure a common set formats
>> for presentation could be agreed upon. Knowing that a change in, say,
>> x86, breaks arm, aarch64, ppc64, s390x would be useful for everyone.
>>
>> Best regards,
>> Stuart
>>
>>
>> On 15/01/17 13:07, Martijn Verburg wrote:
>>
>>> Hi all,
>>>
>>> The LJC has plans to do this with a small build farm for some of the
>>> more common platforms.  This will be for R and academic research
>>> purposes only.
>>>
>>> If you have OpenJDK / Jenkins build experience and would like to help
>>> then please let me know!
>>>
>>> Cheers,
>>> Martijn
>>>
>>> On 13 January 2017 at 20:50, dalibor topic >> > wrote:
>>>
>>>  On 12.01.2017 20:51, Martin Buchholz wrote:
>>>
>>>  Oracle runs tests on many platforms; why does this report only
>>>  include
>>>  one platform?
>>>
>>>
>>>  It would be rather nice to see more people run the OpenJDK jtreg
>>>  tests on their own OpenJDK builds on platforms of their choice and
>>>  post the results regularly.
>>>
>>>  The great thing about these tests is that it doesn't have to be
>>>  someone at Oracle doing all the running and all the posting.
>>>
>>>  cheers,
>>>  dalibor topic
>>>  --
>>>   Dalibor Topic | Principal Product Manager
>>>  Phone: +494089091214  >>  > | Mobile: +491737185961
>>> 
>>>  >
>>>
>>>  ORACLE Deutschland B.V. & Co. KG | Kühnehöfe 5 | 22761 Hamburg
>>>
>>>  ORACLE Deutschland B.V. & Co. KG
>>>  Hauptverwaltung: Riesstr. 25, D-80992 München
>>>  Registergericht: Amtsgericht München, HRA 95603
>>>
>>>  Komplementärin: ORACLE Deutschland Verwaltung B.V.
>>>  Hertogswetering 163/167, 3543 AS Utrecht, Niederlande
>>>  Handelsregister der Handelskammer Midden-Niederlande, Nr. 30143697
>>>  Geschäftsführer: Alexander van der Ven, Jan Schultheiss, Val Maher
>>>
>>>  >>  > Oracle is committed to
>>> developing
>>>  practices and products that help protect the environment
>>>
>>>
>>>
>

Re: JDK 9 build 151 test results now available

[Jonathan Gibbons]

If someone can collect the different sets of jtreg output, there's a 
related utility called "jtdiff" that can be used to generate combined 
reports.  It can compare either full work directories, or the 
report/text/summary.txt files. The latter may be sufficient in this case.


-- Jon


On 1/16/17 3:54 AM, Stuart Monteith wrote:

Hello,
I'm Stuart Monteith in Linaro, working on OpenJDK on ARM's 64-bit
Aarch64 platform. We currently publish aarch64 testing results to the
aarch64-port-dev mailing list and host results on
http://openjdk.linaro.org/ . What I would find useful would be a means
to collate results across all the platforms, with perhaps a method to
collate results from separate build farms. I'm sure a common set formats
for presentation could be agreed upon. Knowing that a change in, say,
x86, breaks arm, aarch64, ppc64, s390x would be useful for everyone.

Best regards,
Stuart


On 15/01/17 13:07, Martijn Verburg wrote:

Hi all,

The LJC has plans to do this with a small build farm for some of the
more common platforms.  This will be for R and academic research
purposes only.

If you have OpenJDK / Jenkins build experience and would like to help
then please let me know!

Cheers,
Martijn

On 13 January 2017 at 20:50, dalibor topic > wrote:

 On 12.01.2017 20:51, Martin Buchholz wrote:

 Oracle runs tests on many platforms; why does this report only
 include
 one platform?


 It would be rather nice to see more people run the OpenJDK jtreg
 tests on their own OpenJDK builds on platforms of their choice and
 post the results regularly.

 The great thing about these tests is that it doesn't have to be
 someone at Oracle doing all the running and all the posting.

 cheers,
 dalibor topic
 --
  Dalibor Topic | Principal Product Manager
 Phone: +494089091214  > | Mobile: +491737185961 
 >

 ORACLE Deutschland B.V. & Co. KG | Kühnehöfe 5 | 22761 Hamburg

 ORACLE Deutschland B.V. & Co. KG
 Hauptverwaltung: Riesstr. 25, D-80992 München
 Registergericht: Amtsgericht München, HRA 95603

 Komplementärin: ORACLE Deutschland Verwaltung B.V.
 Hertogswetering 163/167, 3543 AS Utrecht, Niederlande
 Handelsregister der Handelskammer Midden-Niederlande, Nr. 30143697
 Geschäftsführer: Alexander van der Ven, Jan Schultheiss, Val Maher

 > Oracle is committed to developing
 practices and products that help protect the environment

Re: JDK 9 build 151 test results now available

[Stuart Monteith]

Hello,
I'm Stuart Monteith in Linaro, working on OpenJDK on ARM's 64-bit
Aarch64 platform. We currently publish aarch64 testing results to the
aarch64-port-dev mailing list and host results on
http://openjdk.linaro.org/ . What I would find useful would be a means
to collate results across all the platforms, with perhaps a method to
collate results from separate build farms. I'm sure a common set formats
for presentation could be agreed upon. Knowing that a change in, say,
x86, breaks arm, aarch64, ppc64, s390x would be useful for everyone.

Best regards,
   Stuart


On 15/01/17 13:07, Martijn Verburg wrote:
> Hi all,
> 
> The LJC has plans to do this with a small build farm for some of the
> more common platforms.  This will be for R and academic research
> purposes only.
> 
> If you have OpenJDK / Jenkins build experience and would like to help
> then please let me know!
> 
> Cheers,
> Martijn
> 
> On 13 January 2017 at 20:50, dalibor topic  > wrote:
> 
> On 12.01.2017 20:51, Martin Buchholz wrote:
> 
> Oracle runs tests on many platforms; why does this report only
> include
> one platform?
> 
> 
> It would be rather nice to see more people run the OpenJDK jtreg
> tests on their own OpenJDK builds on platforms of their choice and
> post the results regularly.
> 
> The great thing about these tests is that it doesn't have to be
> someone at Oracle doing all the running and all the posting.
> 
> cheers,
> dalibor topic
> -- 
>  Dalibor Topic | Principal Product Manager
> Phone: +494089091214   > | Mobile: +491737185961 
> >
> 
> ORACLE Deutschland B.V. & Co. KG | Kühnehöfe 5 | 22761 Hamburg
> 
> ORACLE Deutschland B.V. & Co. KG
> Hauptverwaltung: Riesstr. 25, D-80992 München
> Registergericht: Amtsgericht München, HRA 95603
> 
> Komplementärin: ORACLE Deutschland Verwaltung B.V.
> Hertogswetering 163/167, 3543 AS Utrecht, Niederlande
> Handelsregister der Handelskammer Midden-Niederlande, Nr. 30143697
> Geschäftsführer: Alexander van der Ven, Jan Schultheiss, Val Maher
> 
>  > Oracle is committed to developing
> practices and products that help protect the environment
> 
> 

Re: JDK 9 build 151 test results now available

[Mani Sarkar]

Is this improvising the existing build farm already on Cloudbees or setting
up a whole new one.

Why is the choice Jenkins, any rationale behind it?

On Sun, 15 Jan 2017 13:08 Martijn Verburg,  wrote:

> Hi all,
>
> The LJC has plans to do this with a small build farm for some of the more
> common platforms.  This will be for R and academic research purposes
> only.
>
> If you have OpenJDK / Jenkins build experience and would like to help then
> please let me know!
>
> Cheers,
> Martijn
>
> On 13 January 2017 at 20:50, dalibor topic 
> wrote:
>
> > On 12.01.2017 20:51, Martin Buchholz wrote:
> >
> >> Oracle runs tests on many platforms; why does this report only include
> >> one platform?
> >>
> >
> > It would be rather nice to see more people run the OpenJDK jtreg tests on
> > their own OpenJDK builds on platforms of their choice and post the
> results
> > regularly.
> >
> > The great thing about these tests is that it doesn't have to be someone
> at
> > Oracle doing all the running and all the posting.
> >
> > cheers,
> > dalibor topic
> > --
> >  Dalibor Topic | Principal Product Manager
> > Phone: +494089091214  | Mobile: +491737185961
> > 
> >
> > ORACLE Deutschland B.V. & Co. KG | Kühnehöfe 5 | 22761 Hamburg
> >
> > ORACLE Deutschland B.V. & Co. KG
> > Hauptverwaltung: Riesstr. 25, D-80992 München
> > Registergericht: Amtsgericht München, HRA 95603
> >
> > Komplementärin: ORACLE Deutschland Verwaltung B.V.
> > Hertogswetering 163/167, 3543 AS Utrecht, Niederlande
> > Handelsregister der Handelskammer Midden-Niederlande, Nr. 30143697
> > Geschäftsführer: Alexander van der Ven, Jan Schultheiss, Val Maher
> >
> >  Oracle is committed to developing
> > practices and products that help protect the environment
> >
>
-- 
@theNeomatrix369 *  |  **Blog
**  |  *LJC Associate & LJC Advocate
(@adoptopenjdk & @adoptajsr programs)
*Meet-a-Project - *MutabilityDetector
*  |  **Bitbucket
* * |  **Github
* * |  **LinkedIn
*
*Come to Devoxx UK 2017:* http://www.devoxx.co.uk/

*Don't chase success, rather aim for "Excellence", and success will come
chasing after you!*

Re: JDK 9 build 151 test results now available

[Martijn Verburg]

Hi all,

The LJC has plans to do this with a small build farm for some of the more
common platforms.  This will be for R and academic research purposes only.

If you have OpenJDK / Jenkins build experience and would like to help then
please let me know!

Cheers,
Martijn

On 13 January 2017 at 20:50, dalibor topic  wrote:

> On 12.01.2017 20:51, Martin Buchholz wrote:
>
>> Oracle runs tests on many platforms; why does this report only include
>> one platform?
>>
>
> It would be rather nice to see more people run the OpenJDK jtreg tests on
> their own OpenJDK builds on platforms of their choice and post the results
> regularly.
>
> The great thing about these tests is that it doesn't have to be someone at
> Oracle doing all the running and all the posting.
>
> cheers,
> dalibor topic
> --
>  Dalibor Topic | Principal Product Manager
> Phone: +494089091214  | Mobile: +491737185961
> 
>
> ORACLE Deutschland B.V. & Co. KG | Kühnehöfe 5 | 22761 Hamburg
>
> ORACLE Deutschland B.V. & Co. KG
> Hauptverwaltung: Riesstr. 25, D-80992 München
> Registergericht: Amtsgericht München, HRA 95603
>
> Komplementärin: ORACLE Deutschland Verwaltung B.V.
> Hertogswetering 163/167, 3543 AS Utrecht, Niederlande
> Handelsregister der Handelskammer Midden-Niederlande, Nr. 30143697
> Geschäftsführer: Alexander van der Ven, Jan Schultheiss, Val Maher
>
>  Oracle is committed to developing
> practices and products that help protect the environment
>

RE: JDK 9 build 151 test results now available

[Muneer Kolarkunnu]

Hi Martin,

 

I logged a bug, HYPERLINK 
"https://bugs.openjdk.java.net/browse/JDK-8172781"JDK-8172781 for the same and 
attached the logs. It is in Linux x64 environment.

 

Regards,

Muneer

 

From: Rory O'Donnell 
Sent: Friday, January 13, 2017 4:08 PM
To: quality-discuss@openjdk.java.net
Subject: Re: JDK 9 build 151 test results now available

 

 

 

On 12/01/2017 19:51, Martin Buchholz wrote:

 

 

On Wed, Jan 11, 2017 at 1:18 AM, Muneer Kolarkunnu mailto:abdul.kolarku...@oracle.com; \nabdul.kolarku...@oracle.com> wrote:



pass   fail   java/util/concurrent/tck/JSR166TestCase.java

---    fail   java/util/concurrent/tck/JSR166TestCase.java#id1

 

I'm maintaining java/util/concurrent/tck/JSR166TestCase, but there is no 
information here for me to diagnose the problem.

---

Oracle runs tests on many platforms; why does this report only include one 
platform?

Martin , as part of the quality outreach we discussed with jugs what platform 
they would like to see posted - Linux was the 
platform of choice. We do run tests on all the other platforms 
internally,however posting one platform is a resource 
constraint. 

Muneer will log a bug for the failing test.

Rgds,Rory




-- 
Rgds,Rory O'Donnell
Quality Engineering Manager
Oracle EMEA , Dublin, Ireland

Re: JDK 9 build 151 test results now available

[Rory O'Donnell]

On 12/01/2017 19:51, Martin Buchholz wrote:



On Wed, Jan 11, 2017 at 1:18 AM, Muneer Kolarkunnu 
> wrote:




pass   fail   java/util/concurrent/tck/JSR166TestCase.java

---fail   java/util/concurrent/tck/JSR166TestCase.java#id1


I'm maintaining java/util/concurrent/tck/JSR166TestCase, but there is 
no information here for me to diagnose the problem.

---
Oracle runs tests on many platforms; why does this report only include 
one platform?
Martin , as part of the quality outreach we discussed with jugs what 
platform they would like to see posted - Linux was the
platform of choice. We do run tests on all the other platforms 
internally,however posting one platform is a resource

constraint.

Muneer will log a bug for the failing test.

Rgds,Rory

--
Rgds,Rory O'Donnell
Quality Engineering Manager
Oracle EMEA , Dublin, Ireland

Re: JDK 9 build 151 test results now available

[Martin Buchholz]

On Wed, Jan 11, 2017 at 1:18 AM, Muneer Kolarkunnu <
abdul.kolarku...@oracle.com> wrote:

>
>
> pass   fail   java/util/concurrent/tck/JSR166TestCase.java
>
> ---fail   java/util/concurrent/tck/JSR166TestCase.java#id1
>

I'm maintaining java/util/concurrent/tck/JSR166TestCase, but there is no
information here for me to diagnose the problem.
---
Oracle runs tests on many platforms; why does this report only include one
platform?