Re: [yocto] [ptest-runner] Added output processing to pytest

2020-05-22 Thread Ross Burton
On Fri, 22 May 2020 at 14:31, Paul Barker wrote: > > We could have a recipe in oe-core with this in, or just drop it into > > the python recipe directly. > > It's packaged on pypi: https://pypi.org/project/betatest/ > > I need to do a new release as I tidied a few things up and added a > subtest

Re: [yocto] [ptest-runner] Added output processing to pytest

2020-05-22 Thread Paul Barker
On Fri, 22 May 2020 at 14:25, Ross Burton wrote: > > On Fri, 22 May 2020 at 10:29, Paul Barker wrote: > > > > On Fri, 22 May 2020 at 10:26, Alexander Kanavin > > wrote: > > > > > > On Fri, 22 May 2020 at 05:54, zangrc wrote: > > >> > > >> + char pytest_append[] = "| sed -e

Re: [yocto] [ptest-runner] Added output processing to pytest

2020-05-22 Thread Ross Burton
On Fri, 22 May 2020 at 10:29, Paul Barker wrote: > > On Fri, 22 May 2020 at 10:26, Alexander Kanavin > wrote: > > > > On Fri, 22 May 2020 at 05:54, zangrc wrote: > >> > >> + char pytest_append[] = "| sed -e 's/\\[...%\\]//g'| sed -e > >> 's/PASSED/PASS/g'| sed -e

[linux-yocto] v5.2.x - stable updates comprising v5.2.41

2020-05-22 Thread Paul Gortmaker
Bruce, Yocto kernel folks: Here is the next 5.2.x stable update "extension" primarily created for the Yocto project, as the next v5.2.x post-EOL release. The content is from an audit of what went into the v5.4.25 to v5.4.29 releases - plus any upstream commits listed as Fixes: for backports in

Re: [yocto] strange formatting of command output on core-image-base

2020-05-22 Thread stefan . wenninger
Hi Raj, you seem to have been spot on. After adding the "packagegroup-core-full-cmdline" to my image all command output looks perfect. This packagegroup was the only relevant difference between core-image-base and core-image-full-cmdline imo. Some package out of this group did the trick. Thank

Re: [yocto] [ptest-runner] Added output processing to pytest

2020-05-22 Thread Paul Barker
On Fri, 22 May 2020 at 10:26, Alexander Kanavin wrote: > > On Fri, 22 May 2020 at 05:54, zangrc wrote: >> >> + char pytest_append[] = "| sed -e 's/\\[...%\\]//g'| sed -e >> 's/PASSED/PASS/g'| sed -e 's/FAILED/FAIL/g'|sed -e 's/SKIPPED/SKIP/g'| awk >> '{if ($NF==\"PASS\" ||

Re: [yocto] [ptest-runner] Added output processing to pytest

2020-05-22 Thread Alexander Kanavin
On Fri, 22 May 2020 at 05:54, zangrc wrote: > + char pytest_append[] = "| sed -e 's/\\[...%\\]//g'| sed -e > 's/PASSED/PASS/g'| sed -e 's/FAILED/FAIL/g'|sed -e 's/SKIPPED/SKIP/g'| awk > '{if ($NF==\"PASS\" || $NF==\"FAIL\" || $NF==\"SKIP\" || $NF==\"XFAIL\" || >

Re: [yocto] deploy GPG keys into images

2020-05-22 Thread Damien LEFEVRE
Thanks for the tip Rudolf! I found out that gpg has a --homedir flag to do the obvious. Since gpg builds a database, I cannot simply copy the key. Knowing that now, I can just create the gpg database via a standard recipe using the native utility package and install the files. -Damien On Tue,

Re: [linux-yocto][linux-yocto-dev standard/xlnx-soc][PATCH 1/2] usb: dwc3: use PROPERTY_ENTRY_BOOL to initialize property entries

2020-05-22 Thread Michal Simek
On 22. 05. 20 4:34, quanyang.w...@windriver.com wrote: > From: Quanyang Wang > > According to commit 5eb5afb07853d6e9 ("usb: dwc3: use proper initializers > for property entries"), property entries should be initialized by proper > initializer macros. If not, the elements "is_inline" and

Re: [linux-yocto][linux-yocto-dev standard/xlnx-soc][PATCH 2/2] firmware: xilinx: make pm_ioctl_id identical to SDK definitions

2020-05-22 Thread Michal Simek
On 22. 05. 20 4:34, quanyang.w...@windriver.com wrote: > From: Quanyang Wang > > The enum pm_ioctl_id should be identical to the definitions in SDK, or > else according to the value of pm_ioctl_id, secure monitor will execute > unexpected instructions. > > Signed-off-by: Quanyang Wang > --- >