All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: Chaitanya Vadrevu <chaitanya.vadrevu@ni.com>,
	 bitbake-devel@lists.openembedded.org
Subject: Re: [bitbake-devel] [PATCH] process.py: Increase bitbake timeout and add logs
Date: Tue, 02 Mar 2021 22:44:24 +0000	[thread overview]
Message-ID: <9865e3f23d13ec4e47cdf7299a0c550a1f4e74ca.camel@linuxfoundation.org> (raw)
In-Reply-To: <20210302215134.11881-1-chaitanya.vadrevu@ni.com>

On Tue, 2021-03-02 at 15:51 -0600, Chaitanya Vadrevu wrote:
> We have started seeing "Unable to connect to bitbake server ..." errors on
> our build farm consistently with 60s timeout. Increasing the timeout to
> 300s and logging every 10s.
> 
> Signed-off-by: Chaitanya Vadrevu <chaitanya.vadrevu@ni.com>
> ---
>  lib/bb/server/process.py | 15 +++++++++++----
>  1 file changed, 11 insertions(+), 4 deletions(-)

Taking a step back, is it reasonable for bitbake to "disappear" 
for more than a minute? I've not wanted to increase this value
too much as for an interactive user its a pretty poor situation to
stall for delays this long.

We're also seeing these on the project autobuilder occasionally,
they seem load related. Have you any monitoring which says what your
build farm is doing when these timeouts happen? Did increasing it to
300s work?

I have a suspicion its IO load related and probably around syncing
files at bitbake exit that there is the issue.

Cheers,

Richard


  reply	other threads:[~2021-03-02 22:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-02 21:51 [PATCH] process.py: Increase bitbake timeout and add logs Chaitanya Vadrevu
2021-03-02 22:44 ` Richard Purdie [this message]
2021-03-02 23:24   ` [bitbake-devel] " Chaitanya Vadrevu
     [not found]   ` <1668AA16CDA346BC.30035@lists.openembedded.org>
2021-03-15 17:05     ` Chaitanya Vadrevu

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=9865e3f23d13ec4e47cdf7299a0c550a1f4e74ca.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=bitbake-devel@lists.openembedded.org \
    --cc=chaitanya.vadrevu@ni.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.