From: Robert Yang <liezhi.yang@windriver.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: bitbake-devel <bitbake-devel@lists.openembedded.org>
Subject: Re: [PATCH] bitbake: Add pyinotify to lib/
Date: Tue, 20 Jan 2015 17:33:37 +0800 [thread overview]
Message-ID: <54BE20F1.7060401@windriver.com> (raw)
In-Reply-To: <1421744147.1798.39.camel@linuxfoundation.org>
On 01/20/2015 04:55 PM, Richard Purdie wrote:
> On Tue, 2015-01-20 at 10:25 +0800, Robert Yang wrote:
>> Hello RP,
>>
>> I've got several errors like the following when the system's load is high,
>> not sure whether related to pyinotify.
>>
>> for example, when do_configure:
>> sh: 0: Cannot fork
>>
>> when do_package or others:
>> Exception: OSError: [Errno 11] Resource temporarily unavailable
>
> We've seen this on the autobuilders too. I don't think this should be
> from the pyinotify changes since the worker process is spawned
> separately and shouldn't hold watches. Its more likely with the kernel
> changes, we created more contention with the performance improvements
> and pushed things "over the edge" to the point where configurations
> which used to work, are now too contented.
>
> Can we install monitoring on these systems and figure out which
> resources are unavailable?
After more thoughts, maybe because of the "max open files" or
"max user processes", I will try to modify them to see what will happen
the day after tomorrow (I can't modify them today or tomorrow).
// Robert
>
> Cheers,
>
> Richard
>
>
>
next prev parent reply other threads:[~2015-01-20 9:33 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 [this message]
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
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=54BE20F1.7060401@windriver.com \
--to=liezhi.yang@windriver.com \
--cc=bitbake-devel@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.org \
/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