testing branch 2010-08-30

testing branch 2010-08-30

[Cliff Brake]

sending again as it appears the last email did not make it ...


---------- Forwarded message ----------
From: Cliff Brake <cliff.brake@gmail.com>
Date: Mon, Aug 30, 2010 at 11:51 AM
Subject: testing branch 2010-08-30
To: openembedded-devel@lists.openembedded.org


Hello,

Last weeks testing cycle was a good success I think -- thanks to all
who participated.

http://wiki.openembedded.net/index.php/Testing

I have tagged the branch with an annotated tag that includes what built:

http://cgit.openembedded.org/cgit.cgi/openembedded/tag/?id=testing_2010-08-23

It seems like we are getting good coverage of target machines,
distros, and host machines.  I would like to add a target to get some
coverage of Qt x11 and Qt embedded.

Ideas on how to make this better are appreciated.

One change from last week -- I renamed the testing-testing branch to
testing-next as I think that is a little more descriptive.

The testing-next branch has been updated for the next testing cycle,
and is ready for builds.  Please see
http://wiki.openembedded.net/index.php/Testing if you would like to
contribute tested combinations.

Thanks,
Cliff

--
=================
http://bec-systems.com



-- 
=================
http://bec-systems.com

Re: testing branch 2010-08-30

[Frans Meulenbroeks]

2010/8/31 Cliff Brake <cliff.brake@gmail.com>:
> sending again as it appears the last email did not make it ...

Cliff, thanks for resending.
It indeed didn't make it or I overlooked it.

I'm planning to set up a build for neek (nios2) /minimal/console-image
(and/or nios2/angstrom/console-image) or our autobuilder, but didn't
get to it.
Also I might see if I can set up a build for ipx4xx (probably using
nslu2 as target) and console-image + cairo + pango (which drags in
lots of other stuff.

Frans
>
>
> ---------- Forwarded message ----------
> From: Cliff Brake <cliff.brake@gmail.com>
> Date: Mon, Aug 30, 2010 at 11:51 AM
> Subject: testing branch 2010-08-30
> To: openembedded-devel@lists.openembedded.org
>
>
> Hello,
>
> Last weeks testing cycle was a good success I think -- thanks to all
> who participated.
>
> http://wiki.openembedded.net/index.php/Testing
>
> I have tagged the branch with an annotated tag that includes what built:
>
> http://cgit.openembedded.org/cgit.cgi/openembedded/tag/?id=testing_2010-08-23
>
> It seems like we are getting good coverage of target machines,
> distros, and host machines.  I would like to add a target to get some
> coverage of Qt x11 and Qt embedded.
>
> Ideas on how to make this better are appreciated.
>
> One change from last week -- I renamed the testing-testing branch to
> testing-next as I think that is a little more descriptive.
>
> The testing-next branch has been updated for the next testing cycle,
> and is ready for builds.  Please see
> http://wiki.openembedded.net/index.php/Testing if you would like to
> contribute tested combinations.
>
> Thanks,
> Cliff
>
> --
> =================
> http://bec-systems.com
>
>
>
> --
> =================
> http://bec-systems.com
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>

Re: testing branch 2010-08-30

[Gary Thomas]

On 08/31/2010 05:05 AM, Cliff Brake wrote:
> sending again as it appears the last email did not make it ...
>
>
> ---------- Forwarded message ----------
> From: Cliff Brake<cliff.brake@gmail.com>
> Date: Mon, Aug 30, 2010 at 11:51 AM
> Subject: testing branch 2010-08-30
> To: openembedded-devel@lists.openembedded.org
>
>
> Hello,
>
> Last weeks testing cycle was a good success I think -- thanks to all
> who participated.
>
> http://wiki.openembedded.net/index.php/Testing
>
> I have tagged the branch with an annotated tag that includes what built:
>
> http://cgit.openembedded.org/cgit.cgi/openembedded/tag/?id=testing_2010-08-23
>
> It seems like we are getting good coverage of target machines,
> distros, and host machines.  I would like to add a target to get some
> coverage of Qt x11 and Qt embedded.

Did you have some machine/distro/image combos in mind?  I can put some
of my machines on this if I know what to build.

Right now, I'm attempting
   MACHINE=qemuarm
   DISTRO=angstrom-2010.x
   IMAGE=opie-kdepim-image
I'm not sure if this combination makes sense, but I thought I'd see
what happens.

>
> Ideas on how to make this better are appreciated.
>
> One change from last week -- I renamed the testing-testing branch to
> testing-next as I think that is a little more descriptive.
>
> The testing-next branch has been updated for the next testing cycle,
> and is ready for builds.  Please see
> http://wiki.openembedded.net/index.php/Testing if you would like to
> contribute tested combinations.
>
> Thanks,
> Cliff
>
> --
> =================
> http://bec-systems.com
>
>
>

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

Re: testing branch 2010-08-30

[Koen Kooi]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 31-08-10 13:05, Cliff Brake wrote:
> sending again as it appears the last email did not make it ...
> 
> 
> ---------- Forwarded message ----------
> From: Cliff Brake <cliff.brake@gmail.com>
> Date: Mon, Aug 30, 2010 at 11:51 AM
> Subject: testing branch 2010-08-30
> To: openembedded-devel@lists.openembedded.org
> 
> 
> Hello,
> 
> Last weeks testing cycle was a good success I think -- thanks to all
> who participated.
> 
> http://wiki.openembedded.net/index.php/Testing

Looking at the wiki it seems that extending tinderbox to show results
for a certain git revision would be a lot easier to maintain, no?

regards,

Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFMfpbXMkyGM64RGpERAiiTAJwOYBvHlDxrJ/eGZr7dYlYCbVSX4ACfQToU
8in4AlIPMuCyA6/7vfK623o=
=sOg9
-----END PGP SIGNATURE-----

Re: testing branch 2010-08-30

[Frans Meulenbroeks]

2010/9/1 Koen Kooi <k.kooi@student.utwente.nl>:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 31-08-10 13:05, Cliff Brake wrote:
>> sending again as it appears the last email did not make it ...
>>
>>
>> ---------- Forwarded message ----------
>> From: Cliff Brake <cliff.brake@gmail.com>
>> Date: Mon, Aug 30, 2010 at 11:51 AM
>> Subject: testing branch 2010-08-30
>> To: openembedded-devel@lists.openembedded.org
>>
>>
>> Hello,
>>
>> Last weeks testing cycle was a good success I think -- thanks to all
>> who participated.
>>
>> http://wiki.openembedded.net/index.php/Testing
>
> Looking at the wiki it seems that extending tinderbox to show results
> for a certain git revision would be a lot easier to maintain, no?
>
> regards,
>
> Koen

Yes. Good idea. Feel free to add it.

Frans

Re: testing branch 2010-08-30

[Cliff Brake]

On Wed, Sep 1, 2010 at 2:09 PM, Koen Kooi <k.kooi@student.utwente.nl> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 31-08-10 13:05, Cliff Brake wrote:
>> sending again as it appears the last email did not make it ...
>>
>>
>> ---------- Forwarded message ----------
>> From: Cliff Brake <cliff.brake@gmail.com>
>> Date: Mon, Aug 30, 2010 at 11:51 AM
>> Subject: testing branch 2010-08-30
>> To: openembedded-devel@lists.openembedded.org
>>
>>
>> Hello,
>>
>> Last weeks testing cycle was a good success I think -- thanks to all
>> who participated.
>>
>> http://wiki.openembedded.net/index.php/Testing
>
> Looking at the wiki it seems that extending tinderbox to show results
> for a certain git revision would be a lot easier to maintain, no?

Thanks for the ideas, and we need to look into using Tinderbox more.
One thing I don't want to loose is the following:

1) a simple table where users can quickly get an idea of what should
build.  It would take some work to get this extracted from the noise
in Tinderbox, though not impossible

2) I'm afraid if we don't have a somewhat manual process with a known
test cycle, pretty soon people will just drop off and quit running
test cycles, especially if there is no easy visibility of results
(speaking to myself first).  How do we keep from getting lazy as
testing is generally not a lot of fun?

3) it will still be some manual work to maintain the "testing" branch
that is buildable for most tested platforms.

To me the biggest problem is actually getting a significant number of
people running test builds, and summarizing these results in a easy
form.  Everything else is secondary at this point.  Going forward, I
would like to automate where we can using tinderbox, etc.

Thanks,
Cliff

-- 
=================
http://bec-systems.com

Re: testing branch 2010-08-30

[Frans Meulenbroeks]

For what it is worth.
I've gotten permission from my company to put a few builds on our
autobuilder provided there can be a small note on the wiki page
acknowledging that they donated the resources for that test.
Guess that is ok.

I still need to set things up, maybe tomorrow. I'll probably start
with a single machine/distro, and probably it will be combo's that the
company has interest in.

Frans.

PS: for building we use http://hudson-ci.org/
Great tool (probably could also be mentioned on the page)

Re: testing branch 2010-08-30

[Paul Menzel]

[-- Attachment #1: Type: text/plain, Size: 787 bytes --]

Am Mittwoch, den 01.09.2010, 23:23 +0200 schrieb Frans Meulenbroeks:
> For what it is worth.
> I've gotten permission from my company to put a few builds on our
> autobuilder provided there can be a small note on the wiki page
> acknowledging that they donated the resources for that test.
> Guess that is ok.
> 
> I still need to set things up, maybe tomorrow. I'll probably start
> with a single machine/distro, and probably it will be combo's that the
> company has interest in.

> PS: for building we use http://hudson-ci.org/
> Great tool (probably could also be mentioned on the page)

Could you document the steps to set that up somewhere. I (and maybe
others) have some resources too and would be interested in how to set up
an autobuilder.


Thanks,

Paul

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 205 bytes --]

Re: testing branch 2010-08-30

[Khem Raj]

On Wed, Sep 1, 2010 at 2:23 PM, Frans Meulenbroeks
<fransmeulenbroeks@gmail.com> wrote:
> For what it is worth.
> I've gotten permission from my company to put a few builds on our
> autobuilder provided there can be a small note on the wiki page
> acknowledging that they donated the resources for that test.

You can use your company name for tester in table just an idea unless
you are looking for flashy logos

> Guess that is ok.
>
> I still need to set things up, maybe tomorrow. I'll probably start
> with a single machine/distro, and probably it will be combo's that the
> company has interest in.
>
> Frans.
>
> PS: for building we use http://hudson-ci.org/
> Great tool (probably could also be mentioned on the page)
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>

Re: testing branch 2010-08-30

[Frans Meulenbroeks]

2010/9/1 Khem Raj <raj.khem@gmail.com>:
> On Wed, Sep 1, 2010 at 2:23 PM, Frans Meulenbroeks
> <fransmeulenbroeks@gmail.com> wrote:
>> For what it is worth.
>> I've gotten permission from my company to put a few builds on our
>> autobuilder provided there can be a small note on the wiki page
>> acknowledging that they donated the resources for that test.
>
> You can use your company name for tester in table just an idea unless
> you are looking for flashy logos

I'm not looking for a flashy logo. Just want to give some credit.
Appending the company name in the tester table is fine with me. I do
want my name here too as the testing is something that I do as a
private initiative, so the company is not involved in or responsible
for the results. They just donate the resources.

Frans

(and to Paul: I'll try to document the steps, but the tool itself has
already been setup, so it would only be on adding a testing project in
it)

Re: testing branch 2010-08-30

[Frans Meulenbroeks]

Short report:

managed to set things up on the autobuilder.
I did a test run building minimal/console-image for neek (nios2).
It failed in os2Stubs.c
Haven't peeked into it, nios2 is probably not something you want to
run X on anyway.

I'll retest with todays version and more formally report back and
report my findings in the wiki.

Frans