Re: [OE-core] [RFC PATCH 4/4] lib/oeqa: add a test target controller for EFI targets

2014-03-21 Thread Otavio Salvador
On Fri, Mar 21, 2014 at 5:57 AM, Stanacar, StefanX wrote: > On Thu, 2014-03-20 at 18:08 -0300, Otavio Salvador wrote: >> On Thu, Mar 20, 2014 at 1:29 PM, Stefan Stanacar >> wrote: > >> > +# test rootfs + kernel >> > +self.rootfs = os.path.join(d.getVar("DEPLOY_DIR_IMAGE", True),

Re: [OE-core] [RFC PATCH 4/4] lib/oeqa: add a test target controller for EFI targets

2014-03-21 Thread Stanacar, StefanX
Hi Otavio, On Thu, 2014-03-20 at 18:08 -0300, Otavio Salvador wrote: > On Thu, Mar 20, 2014 at 1:29 PM, Stefan Stanacar > wrote: > > +# test rootfs + kernel > > +self.rootfs = os.path.join(d.getVar("DEPLOY_DIR_IMAGE", True), > > d.getVar("IMAGE_LINK_NAME", True) + '.tar.gz') >

Re: [OE-core] [RFC PATCH 4/4] lib/oeqa: add a test target controller for EFI targets

2014-03-20 Thread Otavio Salvador
On Thu, Mar 20, 2014 at 1:29 PM, Stefan Stanacar wrote: > The purpose of this module is to deploy a test image on a EFI-enabled hardware > and run our runtime tests. > A bit of background: > - testimage.bbclass uses the concept of TEST_TARGET which is a class name > that is responsible for target

[OE-core] [RFC PATCH 4/4] lib/oeqa: add a test target controller for EFI targets

2014-03-20 Thread Stefan Stanacar
The purpose of this module is to deploy a test image on a EFI-enabled hardware and run our runtime tests. A bit of background: - testimage.bbclass uses the concept of TEST_TARGET which is a class name that is responsible for target deploying. A layer can provide it's own TEST_TARGET. Right now has