JDK 9 build 151 test results now available

Martijn Verburg martijnverburg at gmail.com
Tue Nov 21 21:01:26 UTC 2017


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 <martijnverburg at gmail.com>
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 <jonathan.gibbons at oracle.com
> > 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&D 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 <dalibor.topic at oracle.com
>>>> <mailto:dalibor.topic at oracle.com>> 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
>>>>      --
>>>>      <http://www.oracle.com> Dalibor Topic | Principal Product Manager
>>>>      Phone: +494089091214 <tel:%2B494089091214> <tel:+494089091214
>>>>      <tel:%2B494089091214>> | Mobile: +491737185961
>>>> <tel:%2B491737185961>
>>>>      <tel:+491737185961 <tel:%2B491737185961>>
>>>>
>>>>      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
>>>>
>>>>      <http://www.oracle.com/commitment
>>>>      <http://www.oracle.com/commitment>> Oracle is committed to
>>>> developing
>>>>      practices and products that help protect the environment
>>>>
>>>>
>>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.openjdk.java.net/pipermail/quality-discuss/attachments/20171121/6eb04b41/attachment.html>


More information about the quality-discuss mailing list