From: Robert Yang <liezhi.yang@windriver.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: bitbake-devel <bitbake-devel@lists.openembedded.org>
Subject: Re: [PATCH] bitbake: Add pyinotify to lib/
Date: Fri, 23 Jan 2015 09:11:57 +0800 [thread overview]
Message-ID: <54C19FDD.5050209@windriver.com> (raw)
In-Reply-To: <54C19BCC.7080102@windriver.com>
On 01/23/2015 08:54 AM, Robert Yang wrote:
>
>
> On 01/22/2015 08:50 PM, Burton, Ross wrote:
>>
>> On 22 January 2015 at 09:10, Robert Yang <liezhi.yang@windriver.com
>> <mailto:liezhi.yang@windriver.com>> wrote:
>>
>> I run 5 builds on the same host, each of them is BB_NUMBER_THREADS=32 and
>> PARALLEL_MAKE="-j32", I can get the error every time when "bitbake image".
>> Then I use "ulimit -u 10000", the "bitbake image" works well, and the
>> world is in building.
>>
>>
>> I'd suggest option (3), reducing the amount of parallelism. If you're expecting
>> five builds on the machine, then reducing those values would reduce wasted
>> parallelism - after all you've got over 3000 tasks sleeping.
>
> But I've never seen this error before 2015/01/02, do you know anything about
> what changes cause this issue recently, please ?
I also got errors like when "ulimit -u is 5000":
http://errors.yoctoproject.org/Errors/Search/Details/7896/1/10/a6ea28e3460217496856d2d79667c4bfbd867df9
I think that they are the similar issues.
When I used "ulimit -u 10000", everything is fine, the world builds are OK, too.
BTW., you can use "top -d 2 -b > top.out" to monitor the resources.
// Robert
>
> // Robert
>
>>
>> Ross
prev parent reply other threads:[~2015-01-23 1:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-13 14:11 [PATCH] bitbake: Add pyinotify to lib/ Richard Purdie
2015-01-19 8:10 ` Robert Yang
2015-01-19 10:28 ` Richard Purdie
2015-01-19 22:53 ` Robert Yang
2015-01-20 2:25 ` Robert Yang
2015-01-20 8:55 ` Richard Purdie
2015-01-20 9:06 ` Robert Yang
2015-01-20 9:33 ` Robert Yang
2015-01-22 9:10 ` Robert Yang
2015-01-22 12:50 ` Burton, Ross
2015-01-23 0:54 ` Robert Yang
2015-01-23 1:11 ` Robert Yang [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54C19FDD.5050209@windriver.com \
--to=liezhi.yang@windriver.com \
--cc=bitbake-devel@lists.openembedded.org \
--cc=ross.burton@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox