From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: bitbake-devel@lists.openembedded.org
Subject: Re: [bitbake-devel] [PATCH] process: Ensure writes to connect pipes are flushed
Date: Sat, 30 Mar 2024 22:12:57 +0000 [thread overview]
Message-ID: <f52a5310d770e994f188e1341805a86619898565.camel@linuxfoundation.org> (raw)
In-Reply-To: <17C197520FFD797E.22094@lists.openembedded.org>
On Sat, 2024-03-30 at 16:21 +0000, Richard Purdie via
lists.openembedded.org wrote:
> In looking into a bitbake 'hang' on the autobuilders, it looked
> very much like the server had finished a computation and was looping
> at idle but the UI didn't see it. Adding in some os.fsync() calls
> should
> help avoid this potential problem (but may cause other timeout/IO
> load
> issues unfortunately).
>
> The exception handling is needed since some writes cause the pipe to
> close immediately so the flush would error.
>
> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
> ---
> lib/bb/server/process.py | 4 ++++
> 1 file changed, 4 insertions(+)
I suspect the issue I was debugging was something a little different
(bug in tinfoil test code in sstatetests in OE-Core) and this patch
probably isn't needed.
Cheers,
Richard
parent reply other threads:[~2024-03-30 22:13 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <17C197520FFD797E.22094@lists.openembedded.org>]
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=f52a5310d770e994f188e1341805a86619898565.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=bitbake-devel@lists.openembedded.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).