From: Henning Schild <henning.schild@siemens.com>
To: Baurzhan Ismagulov <ibr@radix50.net>
Cc: <isar-users@googlegroups.com>
Subject: Re: [PATCH v3 0/2] FILESEXTRAPATHS
Date: Fri, 25 Oct 2019 15:22:37 +0200 [thread overview]
Message-ID: <20191025152237.6b6779ab@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <20191025124950.viz5p3cnc2oaf2br@yssyq.m.ilbers.de>
Am Fri, 25 Oct 2019 14:49:50 +0200
schrieb Baurzhan Ismagulov <ibr@radix50.net>:
> On Thu, Oct 17, 2019 at 02:58:54PM +0530,
> vijaikumar.kanagarajan@gmail.com wrote:
> > meta: Add support for FILESEXTRAPATHS
> > Replace FILESPATH with FILESEXTRAPATHS
>
> The patches look good to me and I'd like to apply them. However, I
> get the following unrelated errors in CI:
>
> ERROR: Unable to start bitbake server
> ERROR: Last 10 lines of server log for this session
> (/workspace/build/isar_ibr_devel/65/build/bitbake-cookerdaemon.log):
> Traceback (most recent call last): File
> "/workspace/build/isar_ibr_devel/65/bitbake/lib/bb/daemonize.py",
> line 83, in createDaemon function() File
> "/workspace/build/isar_ibr_devel/65/bitbake/lib/bb/server/process.py",
> line 444, in _startServer self.cooker =
> bb.cooker.BBCooker(self.configuration, self.featureset) File
> "/workspace/build/isar_ibr_devel/65/bitbake/lib/bb/cooker.py", line
> 185, in __init__ self.watcher = pyinotify.WatchManager() File
> "/workspace/build/isar_ibr_devel/65/bitbake/lib/pyinotify.py", line
> 1764, in __init__ raise OSError(err %
> self._inotify_wrapper.str_errno()) OSError: Cannot initialize new
> instance of inotify, Errno=Too many open files (EMFILE)
>
> Has anyone seen this?
Not yet. I think it is a ulimit thing, maybe caused by jenkins or your
hosts distro.
Or maybe our builds actually keep files open and everyone building in
containers means we do not see it. Try "lsof" and regular reboots ;).
You are truly building that directly on a debian buildhost with the
jenkins user having sudo there?
Henning
> With kind regards,
> Baurzhan.
>
next prev parent reply other threads:[~2019-10-25 13:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0191015094118.GA15374@lightning>
2019-10-16 14:37 ` [PATCH v2 " vijaikumar.kanagarajan
2019-10-16 14:37 ` [PATCH v2 1/2] meta: Add support for FILESEXTRAPATHS vijaikumar.kanagarajan
2019-10-16 14:37 ` [PATCH v2 2/2] Replace FILESPATH with FILESEXTRAPATHS vijaikumar.kanagarajan
2019-10-16 17:05 ` [PATCH v2 0/2] FILESEXTRAPATHS Henning Schild
2019-10-17 9:17 ` Vijai Kumar K
2019-10-17 9:28 ` [PATCH v3 " vijaikumar.kanagarajan
2019-10-17 9:28 ` [PATCH v3 1/2] meta: Add support for FILESEXTRAPATHS vijaikumar.kanagarajan
2019-10-17 9:28 ` [PATCH v3 2/2] Replace FILESPATH with FILESEXTRAPATHS vijaikumar.kanagarajan
2019-10-25 12:49 ` [PATCH v3 0/2] FILESEXTRAPATHS Baurzhan Ismagulov
2019-10-25 13:22 ` Henning Schild [this message]
2019-10-25 14:12 ` Baurzhan Ismagulov
2019-10-25 17:17 ` Jan Kiszka
2019-11-04 19:41 ` Baurzhan Ismagulov
2019-11-04 19:45 ` Baurzhan Ismagulov
2019-11-05 16:08 ` Henning Schild
2019-11-05 16:18 ` vijai kumar
2019-11-05 17:07 ` Jan Kiszka
2019-11-05 17:36 ` vijai kumar
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=20191025152237.6b6779ab@md1za8fc.ad001.siemens.net \
--to=henning.schild@siemens.com \
--cc=ibr@radix50.net \
--cc=isar-users@googlegroups.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