Hi, We need genericx86-64 lsb image. It is used for stress testing. Regards, -- Alexandru Georgescu
-----Original Message----- From: Yi Zhao [mailto:yi.z...@windriver.com] Sent: Friday, March 28, 2014 4:24 AM To: Flanagan, Elizabeth Cc: Otavio Salvador; yocto@yoctoproject.org; Georgescu, Alexandru C Subject: Re: Reducing nightly/release build artifacts. Hi Beth, 于 2014年03月27日 05:30, Flanagan, Elizabeth 写道: > A list of exactly what files you use for QA would be grand. > > We can use http://autobuilder.yoctoproject.org/pub/nightly/20140326-1/ > as our base. We don't use all qemu-lsb , beagleboard-lsb, routerstationpro-lsb, and p1022ds-lsb artifacts. For the image type, we don't need minimal-dev and sato-dev. Thanks, Yi > > -b > > On Wed, Mar 26, 2014 at 2:22 PM, Otavio Salvador > <ota...@ossystems.com.br> wrote: >> Hello Beth, >> >> On Wed, Mar 26, 2014 at 6:14 PM, Flanagan, Elizabeth >> <elizabeth.flana...@intel.com> wrote: >>> I'd like to start looking at reducing the number of artifacts we're >>> releasing both for our nightly builds (which is at 250,000 artifacts >>> and .25 TB!) and releases. >>> >>> What I'm thinking is this: >>> >>> Reduce nightly: >>> - Reduce ADT-REPO to just qemu* arches for all builds >>> - If every QA team could provide me a list of what files they >>> actually need I could reduce the published artifacts to *just* what is >>> needed. >>> >>> Reduce releases: >>> - Reduce ADT-REPO to just qemu >>> - Don't release ipk/rpm/debs. Continue to release ipks through ADT >>> - Don't release machines outside of BSP tarball /binary directory >>> >>> If folks who do QA could get me a list of all the files they use, we >>> can start removing excess artifacts. I know this is a balance, but >>> I'd really like us to start targeting our release artifacts to just >>> the things we need. >> I fully agree on that. >> >> Is there anything you need specifically from me? >> >> -- >> Otavio Salvador O.S. Systems >> http://www.ossystems.com.br http://code.ossystems.com.br >> Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750 > > -- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto