All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luca Ceresoli <luca.ceresoli@bootlin.com>
To: "Mikko Rapeli" <mikko.rapeli@bmw.de>
Cc: bitbake-devel@lists.openembedded.org
Subject: Re: [bitbake-devel] [PATCH] event.py: ignore exceptions from stdout and sterr operations in atexit
Date: Thu, 9 Jun 2022 08:57:54 +0200	[thread overview]
Message-ID: <20220609085754.22144287@booty> (raw)
In-Reply-To: <20220609055610.29857-1-mikko.rapeli@bmw.de>

Hi Mikko,

On Thu,  9 Jun 2022 08:56:10 +0300
"Mikko Rapeli" <mikko.rapeli@bmw.de> wrote:

> From: Mikko Rapeli <mikko.rapeli@bmw.de>
> 
> When atexit functions run, stdout and stderr operations may fail, e.g.
> when output is piped to less but has been exited by the user.
> This removes error print from output of "bitbake -e sqlite3 | less"
> if user presses "q" before bitbake has finished processing:
> 
> [Errno 32] Broken pipeError in atexit._run_exitfuncs:
> Traceback (most recent call last):
>   File "/home/builder/src/poky/bitbake/lib/bb/event.py", line 135, in print_ui_queue
>     sys.stdout.flush()
> 
> Signed-off-by: Mikko Rapeli <mikko.rapeli@bmw.de>
> ---
>  bitbake/lib/bb/event.py | 10 ++++++++--
>  1 file changed, 8 insertions(+), 2 deletions(-)
> 
> diff --git a/bitbake/lib/bb/event.py b/bitbake/lib/bb/event.py
> index df020551e3..97668601a1 100644
> --- a/bitbake/lib/bb/event.py

        ^^^^^^^^

This patch does not apply on the bitbake tree due to the extra
'bitbake/' directory component. Perhaps you generated it from a poky
tree instead?

I removed the extra component and applied it however, thus no need to
resend, and also:

Tested-by: Luca Ceresoli <luca.ceresoli@bootlin.com>

-- 
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com


      reply	other threads:[~2022-06-09  6:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-09  5:56 [PATCH] event.py: ignore exceptions from stdout and sterr operations in atexit mikko.rapeli
2022-06-09  6:57 ` Luca Ceresoli [this message]

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=20220609085754.22144287@booty \
    --to=luca.ceresoli@bootlin.com \
    --cc=bitbake-devel@lists.openembedded.org \
    --cc=mikko.rapeli@bmw.de \
    /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.