coffee tasters guild

[David Herron-2]

Let's restart this as a new thread ...

The idea in the back of my mind which I've not made time for would be "The
Coffee Tasters Guild".  Purpose, group organized OpenJDK builds and test
results stashed on a common website.

Why that name?  If it's organized not as an official OpenJDK project I think
it might be a problem to use the OpenJDK trademark.  Besides there can never
be too many coffee puns when it comes to Java.

That's my strawman,

- David Herron
http://davidherron.com

[Frans Thamura-2]

On Mon, Jun 1, 2009 at 2:14 AM, David Herron <david@...> wrote:
> Let's restart this as a new thread ...
>
> The idea in the back of my mind which I've not made time for would be "The
> Coffee Tasters Guild".  Purpose, group organized OpenJDK builds and test
> results stashed on a common website.

what is the result of this test?


we test all the openjdk right?

can i know, how to join this project

F

[David Herron-2]

On Sun, May 31, 2009 at 12:25 PM, Frans Thamura <frans@...> wrote:

> On Mon, Jun 1, 2009 at 2:14 AM, David Herron <david@...>
> wrote:
> > Let's restart this as a new thread ...
> >
> > The idea in the back of my mind which I've not made time for would be
> "The
> > Coffee Tasters Guild".  Purpose, group organized OpenJDK builds and test
> > results stashed on a common website.
>
> what is the result of this test?
>
>
> we test all the openjdk right?
>
> can i know, how to join this project
>
> F
>

Maybe I wasn't clear enough.  I wasn't making an announcement of an existing
project, just describing one I'd had in mind.

BTW it doesn't have to be complicated.  It could just be a common web site
where several people have ssh access to upload stuff.

- David Herron
http://davidherron.com

[kelly.ohair]

David Herron wrote:

> On Sun, May 31, 2009 at 12:25 PM, Frans Thamura <frans@...> wrote:
>
>> On Mon, Jun 1, 2009 at 2:14 AM, David Herron <david@...>
>> wrote:
>>> Let's restart this as a new thread ...
>>>
>>> The idea in the back of my mind which I've not made time for would be
>> "The
>>> Coffee Tasters Guild".  Purpose, group organized OpenJDK builds and test
>>> results stashed on a common website.
>> what is the result of this test?
>>
>>
>> we test all the openjdk right?
>>
>> can i know, how to join this project
>>
>> F
>>
>
> Maybe I wasn't clear enough.  I wasn't making an announcement of an existing
> project, just describing one I'd had in mind.
>
> BTW it doesn't have to be complicated.  It could just be a common web site
> where several people have ssh access to upload stuff.

Anyone in the people list at http://db.openjdk.java.net/people
can start doing this anytime using the current cr.openjdk.java.net site.
You can sftp into it as described in http://cr.openjdk.java.net/,
create a 'stuff' directory to hold things and then you can then
    scp -r directory_of_stuff/ cr.openjdk.java.net:stuff/
   (or rsync)
Then anyone can access it via
    http://cr.openjdk.java.net/~USER/stuff
where USER is the openjdk user name that published the stuff.

Maybe not a permanent answer, but we can start with something like that.
Only open stuff please, none of that poisonous proprietary stuff... ;^)

But you need to be in the contributor list to populate anything here
(e.g. listed in http://db.openjdk.java.net/people)

-kto

>
> - David Herron
> http://davidherron.com

[Mark Wielaard]

Hi David,

On Sun, 2009-05-31 at 12:14 -0700, David Herron wrote:
> Let's restart this as a new thread ...
>
> The idea in the back of my mind which I've not made time for would be "The
> Coffee Tasters Guild".  Purpose, group organized OpenJDK builds and test
> results stashed on a common website.

Xerxes reminded me that Omair already has setup something like that for
collecting and displaying results from jtreg and mauve runs:
http://icedtea.classpath.org/~omajid/testing.html
(Although it seems his builder stopped somewhere last month)

It even comes with the python scripts to control the whole thing
(wish I remembered that when I hacked up my quick-and-dirty bash script)
Connecting such reports with some autobuilders and some place to collect
the test results so you can easily compare between runs would indeed be
really cool.

A plain text file with one-line per fail/pass would proably be easiest.
Currently the icedtea builder publishes the whole jtreg JTReport and
JTwork dir including .jti files for the hotspot/langtools/jdk so you can
easily analyze why something failed in that particular build setup.
http://icedtea.classpath.org/builds/icedtea6/test/
But that is not very space efficient (even when compressed).

Cheers,

Mark