From: Anton Mikanovich <amikan@ilbers.de>
To: isar-users <isar-users@googlegroups.com>,
Jan Kiszka <jan.kiszka@siemens.com>,
Baurzhan Ismagulov <ibr@ilbers.de>
Subject: Re: [PATCH] utils: Ensure shell function failure in python logging is correct
Date: Thu, 26 May 2022 12:54:40 +0300 [thread overview]
Message-ID: <6a0a98bb-2381-7378-90d7-482159b4065b@ilbers.de> (raw)
In-Reply-To: <20220526094739.6340-1-amikan@ilbers.de>
26.05.2022 12:47, Anton Mikanovich wrote:
> If a python function exec_func() calls a shell task, the logging wasn't working
> correctly in all cases since the exception was turned into a BBHandledException()
> and the logfile piece was lost which is handled at the top task level.
>
> The easiest way to avoid this is to allow the ExecutionError exceptions to
> be raised to a higher level, we don't need the traceback for them.
>
> Backported from Bitbake 2.0 upstream branch:
> https://git.openembedded.org/bitbake/commit/?id=7cae11f558f9ff5fd05ef23b789aaef92fb5a327
>
> Signed-off-by: Anton Mikanovich <amikan@ilbers.de>
This is temporary backport until we will migrate to the new Bitbake version
(requires override syntax fix for all the layers).
We are using 1.50 Bitabake branch which is already in 'End of life' state.
Branch 1.52 includes the fix, but will be EOL this month.
So we should migrate to Bitbake 2.0 branch which is LTS and will be
supported
for the next 2 years minimum.
next prev parent reply other threads:[~2022-05-26 9:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-26 9:47 Anton Mikanovich
2022-05-26 9:54 ` Anton Mikanovich [this message]
2022-05-27 7:53 ` Florian Bezdeka
2022-05-27 7:57 ` Anton Mikanovich
2022-05-27 8:07 ` Baurzhan Ismagulov
2022-05-27 12:59 ` Jan Kiszka
2022-06-02 11:28 ` Anton Mikanovich
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=6a0a98bb-2381-7378-90d7-482159b4065b@ilbers.de \
--to=amikan@ilbers.de \
--cc=ibr@ilbers.de \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.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