From: Richard Purdie <firstname.lastname@example.org>
To: Qi.Chen@windriver.com, email@example.com
Subject: Re: [bitbake-devel][PATCH] bitbake: add --noreply-timeout option
Date: Wed, 10 May 2023 08:52:04 +0100 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
On Wed, 2023-05-10 at 11:16 +0800, Chen Qi via lists.openembedded.org
> From: Chen Qi <Qi.Chen@windriver.com>
> For now, if the client gets no reply from server when running a
> command, it exits after a period of time. The value is currently
> 60s. Looking at the history, this value was increased from 8s to
> 30s, and then it was increased again to 60s.
> For now, what I can see is that when running one world build on a
> 128 core, 512G server, starting a second build has a chance to fail
> at updateConfig.
> Instead of increasing this value again and again, let's add an option
> for easier customization of this value.
> Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
> bitbake/lib/bb/main.py | 7 ++++++-
> bitbake/lib/bb/server/process.py | 19 ++++++++++---------
> 2 files changed, 16 insertions(+), 10 deletions(-)
You're saying that the server can take over a minute to start up and
this is considered acceptable?
What configuration is the other world build running with? I'd suggest
the system is so overloaded it isn't useful any more and you should
have pressure control enabled or other mechanisms to allow the system
I'm not keen to make this any more configurable as 60s should be enough
and if it isn't, there are different issues at play.
Having bitbake silently hang for minutes at a time isn't good for users
and isn't good for CI either.
next prev parent reply other threads:[~2023-05-10 7:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-10 3:16 [bitbake-devel][PATCH] bitbake: add --noreply-timeout option Qi.Chen
2023-05-10 7:52 ` Richard Purdie [this message]
2023-05-10 9:43 ` Chen, Qi
2023-05-10 10:35 ` Richard Purdie
2023-05-10 11:40 ` Chen, Qi
[not found] ` <175DC558A674BAA1.email@example.com>
2023-05-10 15:05 ` Chen, Qi
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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;
as well as URLs for NNTP newsgroup(s).