Re: OpenEmbbedded as a test suite next steps

2012-03-09 Thread Ken Werner
On 03/08/2012 07:53 PM, Denys Dmytriyenko wrote: On Thu, Mar 08, 2012 at 07:08:51PM +0100, Ken Werner wrote: On 03/08/2012 09:03 AM, Marcin Juszkiewicz wrote: Just to give you an overview. The build of the sato and qt4e images takes about two hours my machine (24x "E5649 @ 2.53GHz" with 32gb o

Re: OpenEmbbedded as a test suite next steps

2012-03-08 Thread Michael Hope
On 9 March 2012 10:36, Ramana Radhakrishnan wrote: > On 8 March 2012 21:24, Michael Hope wrote: >> On 9 March 2012 07:08, Ken Werner wrote: >>> On 03/08/2012 09:03 AM, Marcin Juszkiewicz wrote: >>> Ah, thanks - I forgot about that. It saves about 16GB of space and running >>> on tmpfs saves

Re: OpenEmbbedded as a test suite next steps

2012-03-08 Thread Ramana Radhakrishnan
On 8 March 2012 21:24, Michael Hope wrote: > On 9 March 2012 07:08, Ken Werner wrote: >> On 03/08/2012 09:03 AM, Marcin Juszkiewicz wrote: >>> >> Ah, thanks - I forgot about that. It saves about 16GB of space and running >> on tmpfs saves about 30 minutes on my setup. Thanks! > > You can build a

Re: OpenEmbbedded as a test suite next steps

2012-03-08 Thread Michael Hope
On 9 March 2012 07:08, Ken Werner wrote: > On 03/08/2012 09:03 AM, Marcin Juszkiewicz wrote: >> >> W dniu 07.03.2012 22:47, Ken Werner pisze: >> I had setup at least two buildbots building OE images. For testing of >> Linaro toolchain it can be used too I think. If buildbot has ability to >> pull

Re: OpenEmbbedded as a test suite next steps

2012-03-08 Thread Denys Dmytriyenko
On Thu, Mar 08, 2012 at 07:08:51PM +0100, Ken Werner wrote: > On 03/08/2012 09:03 AM, Marcin Juszkiewicz wrote: > >>Just to give you an overview. The build of the sato and qt4e images > >>takes about two hours my machine (24x "E5649 @ 2.53GHz" with 32gb of > >>RAM) and creates about 37GiB of objec

Re: OpenEmbbedded as a test suite next steps

2012-03-08 Thread Ken Werner
On 03/08/2012 09:03 AM, Marcin Juszkiewicz wrote: W dniu 07.03.2012 22:47, Ken Werner pisze: On 03/06/2012 01:26 AM, Michael Hope wrote: Talking: Say Hi to Validation re: EC2 and plans Say Hi to the ARM landing team re: vexpress upstream support Say Hi to Beth Flanagan re: Yocto's existing au

Re: OpenEmbbedded as a test suite next steps

2012-03-08 Thread Marcin Juszkiewicz
W dniu 07.03.2012 22:47, Ken Werner pisze: > On 03/06/2012 01:26 AM, Michael Hope wrote: >> Talking: >> Say Hi to Validation re: EC2 and plans >> Say Hi to the ARM landing team re: vexpress upstream support >> Say Hi to Beth Flanagan re: Yocto's existing auto builders and any hints > > Yep, it lo

Re: OpenEmbbedded as a test suite next steps

2012-03-07 Thread Fathi Boudra
On 7 March 2012 23:47, Ken Werner wrote: > On 03/06/2012 01:26 AM, Michael Hope wrote: >> >> Hi Ken.  In follow up to our 1-on-1 yesterday, here's what I'd like done >> next. >> >> The goal is to use OE Core as a release test suite.  The releases are >> tarballs so we can keep the current recipe f

Re: OpenEmbbedded as a test suite next steps

2012-03-07 Thread Ken Werner
On 03/06/2012 01:26 AM, Michael Hope wrote: Hi Ken. In follow up to our 1-on-1 yesterday, here's what I'd like done next. The goal is to use OE Core as a release test suite. The releases are tarballs so we can keep the current recipe format and punt bzr support for later. The first step is to

OpenEmbbedded as a test suite next steps

2012-03-05 Thread Michael Hope
Hi Ken. In follow up to our 1-on-1 yesterday, here's what I'd like done next. The goal is to use OE Core as a release test suite. The releases are tarballs so we can keep the current recipe format and punt bzr support for later. The first step is to be able to reliably build a release in the cl