> -Original Message-
> From: openembedded-core-boun...@lists.openembedded.org
> [mailto:openembedded-core-boun...@lists.openembedded.org] On Behalf
> Of Burton, Ross
> Sent: Wednesday, September 03, 2014 5:59 PM
> To: Musat, GeorgeX L
> Cc: OE-core
> Subject: Re: [OE-core] [PATCH 1/2] oeq
Hello,
>From my experience with ptest, there will always be a few tests failing, so we
>will always get exit code 1. Should this better return exit code 0 if the
>individual tests performed correctly(weather they passed or failed) and 1 if
>there were any errors during the running of the tests?
Hello Eric,
I am happy to see you are also working on this. We already have 2 features that
should be implemented in 1.7 related to this that should help along with
integrating ptest with automated tests. These features use the current
‘testimage’ framework that runs runtime tests on both QEMU
Yes, thank you! This slipped through our fingers.
> -Original Message-
> From: openembedded-core-boun...@lists.openembedded.org
> [mailto:openembedded-core-boun...@lists.openembedded.org] On Behalf
> Of Paul Eggleton
> Sent: Friday, July 25, 2014 7:16 PM
> To: openembedded-core@lists.opene
> -Original Message-
> From: Stefan Stanacar [mailto:sst...@gmail.com]
> Sent: Saturday, June 07, 2014 5:09 PM
> To: Stoicescu, CorneliuX
> Cc: openembedded-core@lists.openembedded.org
> Subject: Re: [OE-core] [PATCH V2 7/7] scripts/test-remote-image: Add script
>
> -Original Message-
> From: Stefan Stanacar [mailto:sst...@gmail.com]
> Sent: Saturday, June 07, 2014 3:39 PM
> To: Stoicescu, CorneliuX
> Cc: openembedded-core@lists.openembedded.org
> Subject: Re: [OE-core] [PATCH V2 6/7] controllers/masterimage.py: Make
> te
> -Original Message-
> From: Stefan Stanacar [mailto:sst...@gmail.com]
> Sent: Saturday, June 07, 2014 2:38 PM
> To: Stoicescu, CorneliuX
> Cc: openembedded-core@lists.openembedded.org
> Subject: Re: [OE-core] [PATCH V2 1/7] targetcontrol.py: make possible
> dynam
> -Original Message-
> From: Saul Wold [mailto:s...@linux.intel.com]
> Sent: Tuesday, May 27, 2014 5:24 PM
> To: Stefan Stanacar; Stoicescu, CorneliuX
> Cc: openembedded-core@lists.openembedded.org
> Subject: Re: [OE-core] [PATCH] oeqa/controllers/beaglebonetarget.py
> -Original Message-
> From: Stoicescu, CorneliuX
> Sent: Tuesday, May 27, 2014 10:02 AM
> To: 'Anders Darander'
> Cc: openembedded-core@lists.openembedded.org
> Subject: RE: [OE-core] [PATCH] oeqa/controllers/beaglebonetarget.py: add
> condi
> -Original Message-
> From: Anders Darander [mailto:and...@chargestorm.se]
> Sent: Tuesday, May 27, 2014 9:46 AM
> To: Stoicescu, CorneliuX
> Cc: openembedded-core@lists.openembedded.org
> Subject: Re: [OE-core] [PATCH] oeqa/controllers/beaglebonetarget.py: add
>
> -Original Message-
> From: openembedded-core-boun...@lists.openembedded.org
> [mailto:openembedded-core-boun...@lists.openembedded.org] On Behalf
> Of Stefan Stanacar
> Sent: Monday, May 19, 2014 12:28 PM
> To: Musat, GeorgeX L
> Cc: openembedded-core@lists.openembedded.org
> Subject: R
> > 1) Testing recipes updates or new recipes
> >
> > Even though we cannot test every single scenario or the functionality of a
> recipe, we could create a test suite that would:
> > - build the recipe with all major architectures(qemux86, qemux86-64,
> > qemuarm, qemuppc, qemumips)
> > - rebui
Hello,
During the 1.6 development/testing cycle we introduced and used oe-selftest
more and more for QA purposes to identify various issues in the master branch.
For those who don't know yet what is oe-selftest, it is a python unit test
based testing framework designed to simulate poky external
WW15:
- OOO WW15.4
- Finished 1.6 M5 RC2 Full Pass
- Started 1.6 M5 RC4 Full Pass
- Verified QA owned bugs
- Tried to boot beaglebone image on a beaglebone black board. The
kernel had some issues and are logged in this bug:
https://bugzilla.yoctoproject.o
I can.
Regards,
Corneliu
> -Original Message-
> From: Stoicescu, CorneliuX
> Sent: Monday, February 17, 2014 6:09 PM
> To: openembedded-core@lists.openembedded.org
> Cc: Stoicescu, CorneliuX
> Subject: [PATCH] oe-selftest: Fixed "test_rm_old_image" that was outdated
&
I forgot a few comment lines. I will resend the patch.
> -Original Message-
> From: Stoicescu, CorneliuX
> Sent: Friday, January 17, 2014 1:11 PM
> To: openembedded-core@lists.openembedded.org
> Cc: Stoicescu, CorneliuX
> Subject: [PATCH] oe-selftest: Patch sstate test
> > --- a/meta/classes/buildhistory.bbclass
> > +++ b/meta/classes/buildhistory.bbclass
> > @@ -16,9 +16,12 @@ BUILDHISTORY_IMAGE_FILES ?= "/etc/passwd
> /etc/group"
> > BUILDHISTORY_COMMIT ?= "0"
> > BUILDHISTORY_COMMIT_AUTHOR ?= "buildhistory
> "
> > BUILDHISTORY_PUSH_REPO ?= ""
> > +BUILDSTAT
> -Original Message-
> From: Richard Purdie [mailto:richard.pur...@linuxfoundation.org]
> Sent: Monday, November 04, 2013 2:35 PM
> To: Paul Eggleton
> Cc: Stoicescu, CorneliuX; openembedded-core@lists.openembedded.org
> Subject: Re: [OE-core] [PATCH] Modify build
> -Original Message-
> From: Richard Purdie [mailto:richard.pur...@linuxfoundation.org]
> Sent: Monday, November 04, 2013 11:16 AM
> To: Stoicescu, CorneliuX
> Cc: openembedded-core@lists.openembedded.org
> Subject: Re: [OE-core] [PATCH] Modify buildstats t
> -Original Message-
> From: Richard Purdie [mailto:richard.pur...@linuxfoundation.org]
> Sent: Friday, November 01, 2013 8:07 PM
> To: Stoicescu, CorneliuX
> Cc: openembedded-core@lists.openembedded.org
> Subject: Re: [OE-core] [PATCH] Modify buildstats t
Thank you for the reply, Paul. I will make sure to make the most of your input!
> -Original Message-
> From: Paul Eggleton [mailto:paul.eggle...@linux.intel.com]
> Sent: Thursday, October 31, 2013 12:34 PM
> To: Stoicescu, CorneliuX
> Cc: openembedded-core@lists.openembedde
Hello all,
This e-mail was originally sent to the Yocto mailing list in the form of 2
e-mails. As per Paul's and Richard's request, I am re-sending and moving the
conversation here. Feel free to add any input :) .
NOTE: I also made a small syntax correction in the example at the end of the
e-m
22 matches
Mail list logo
