Re: [OE-core] [PATCH] utils.py: add parallel make helpers

On Sat, Feb 17, 2018 at 4:48 PM Joshua Watt wrote: > > > On Feb 17, 2018 18:25, "Khem Raj" wrote: > > > > On 2/16/18 12:14 PM, Martin Jansa wrote: > >> +v = max(limit, v) >> >> this seems to be doing the opposite of what the limit was used

Re: [OE-core] [PATCH] utils.py: add parallel make helpers

On Feb 17, 2018 18:25, "Khem Raj" wrote: On 2/16/18 12:14 PM, Martin Jansa wrote: > +v = max(limit, v) > > this seems to be doing the opposite of what the limit was used for before: > > -v = min(64, int(v)) > > moreover, I think the limit should

Re: [OE-core] [PATCH] cve-check: put log in T so it doesn't get deleted by rm_work

Because I failed to post them to the list and Richard merged a chunk of MUT on my approval, forgetting that I hadn't posted them. My mistake, apologies. Ross On 17 February 2018 at 14:38, Alexander Kanavin < alexander.kana...@linux.intel.com> wrote: > On 02/09/2018 01:09 AM, Ross Burton wrote:

Re: [OE-core] [PATCH] utils.py: add parallel make helpers

On 2/16/18 12:14 PM, Martin Jansa wrote: +            v = max(limit, v) this seems to be doing the opposite of what the limit was used for before: -                v = min(64, int(v)) moreover, I think the limit should be based on ncpu() instead of hard coding it. On Mon, Feb 12, 2018

Re: [OE-core] [PATCH] pseudo: update to latest master

On Sat, 17 Feb 2018 15:28:55 +0200 Alexander Kanavin wrote: > For me, with epoll enabled: > > b6a015a works > 23f089f and 26e30fa both lock up Huh. It's possible that the initial "don't try to close fd 0" was correct, and the real problem is that the attempt

Re: [OE-core] [PATCH 2/9] linux-yocto: introduce 4.15 recipes

cool. Thanks, I was wondering how it went. I'll submit my two patches this weekend to the list, since I have one minor tweak to the make-mod-scripts to do first. Cheers, Bruce On 2018-02-17 7:52 AM, Martin Jansa wrote: This last version seems to build fine for me (I haven't tried more than

[OE-core] [PATCH 2/2] siteinfo: add aarch64_illp32 decode

Signed-off-by: Armin Kuster --- meta/classes/kernel-arch.bbclass | 2 ++ 1 file changed, 2 insertions(+) diff --git a/meta/classes/kernel-arch.bbclass b/meta/classes/kernel-arch.bbclass index e0fe22b..09793fc 100644 --- a/meta/classes/kernel-arch.bbclass +++

[OE-core] [PATCH 1/2] update-rc.d: QA regression.

I noticed many new QA warning with arm64 mulitlib suspicious values 'initd-functions-dev' in RRECOMMENDS [multilib] I believe this is a regression via commit http://cgit.openembedded.org/openembedded-core/commit/meta/classes/update-rc.d.bbclass?id=cdcebd81c872cb7386c658998e27cf24e1d0447c

Re: [OE-core] [PATCH] cve-check: put log in T so it doesn't get deleted by rm_work

On 02/09/2018 01:09 AM, Ross Burton wrote: This is where the other task logs go, so it's a sensible place to put it. There is a bunch of other cve-check related commits in master now that were never posted here, why is that? Alex -- ___

Re: [OE-core] [PATCH] pseudo: update to latest master

On 02/17/2018 02:03 PM, Martin Jansa wrote: > Without this change (pseudo at 'Handle O_TMPFILE more better') things work flawlessly, with epoll enabled. Your http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=akanavin/pseudo-1.9.0 is using this change with SRCREV 

Re: [OE-core] [PATCH 2/9] linux-yocto: introduce 4.15 recipes

This last version seems to build fine for me (I haven't tried more than building lttng-modules which were failing before, because of some other issues elsewhere). On Thu, Feb 15, 2018 at 6:59 PM, Bruce Ashfield < bruce.ashfi...@windriver.com> wrote: > On 02/15/2018 11:37 AM, Martin Jansa wrote:

Re: [OE-core] [PATCH] pseudo: update to latest master

> Without this change (pseudo at 'Handle O_TMPFILE more better') things work flawlessly, with epoll enabled. Your http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=akanavin/pseudo-1.9.0 is using this change with SRCREV b6a015aa91d7ab84c2f5466f3b5704f501129cbc. Does it mean that the

Re: [OE-core] [PATCH] pseudo: update to latest master

On ubuntu-14.04 I'm seeing SIGABRT in couple do_install tasks even after reverting both pseudo changes (the upgrade from Alex as well as SRCREV bump to latest commit from Seebs). So there might be different root cause for SIGABRT unrelated to pseudo which I haven't seen before, because pseudo

Re: [OE-core] [PATCH] pseudo: update to latest master

On 02/16/2018 09:25 PM, Seebs wrote: On Fri, 16 Feb 2018 20:11:48 +0100 Martin Jansa wrote: I didn't get to the logs yet, but with this change added I see many do_install tasks failing with exit code '134'. Huh, that's SIGABRT. I'll see if I can reproduce. My