public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Baurzhan Ismagulov <ibr@radix50.net>
To: isar-users@googlegroups.com
Subject: Re: [PATCH v3 0/2] FILESEXTRAPATHS
Date: Fri, 25 Oct 2019 16:12:12 +0200	[thread overview]
Message-ID: <20191025141211.akcckhitwg7igf4g@yssyq.m.ilbers.de> (raw)
In-Reply-To: <20191025152237.6b6779ab@md1za8fc.ad001.siemens.net>

Hello Henning,

thanks for the response.

On Fri, Oct 25, 2019 at 03:22:37PM +0200, Henning Schild wrote:
> 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 ;).

I'd like to understand the problem before I start playing with the knobs :) .
Moving to a different container solution or rebooting wouldn't solve the
underlying problem. Besides, I'm not sure this problem doesn't affect e.g.
docker, since ulimits are per-process, and this one occurred during bitbake -e
in start_vm.

With kind regards,
Baurzhan.

  reply	other threads:[~2019-10-25 14:12 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
2019-10-25 14:12           ` Baurzhan Ismagulov [this message]
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=20191025141211.akcckhitwg7igf4g@yssyq.m.ilbers.de \
    --to=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