Re: [PATCH] utils: Ensure shell function failure in python logging is correct

[Jan Kiszka <jan.kiszka@siemens.com>]

On 27.05.22 10:07, Baurzhan Ismagulov wrote:
> On Fri, May 27, 2022 at 09:53:24AM +0200, Florian Bezdeka wrote:
>> On 26.05.22 11: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.
>>
>> Upstream first? Why can't we ask bitbake guys to do the backport and
>> lift our bitbake version afterwards? Is that already ongoing?
> 
> We had checked https://wiki.yoctoproject.org/wiki/Releases:
> 
> * 1.50 is EOL
> * 1.52 is untested with Isar and its support ends on Tue
> 
> That is why I think the optimal next step is to migrate to bitbake 2.0 after
> the upcoming Isar release. This patch addresses the request to get the problem
> fixed ASAP before the release. If anyone volunteers to drive the upstream
> discussion -- I don't have anything against it, but I'd be reluctant to delay
> the Isar release if it takes longer.
> 

Agreed, we will very likely not have the power to re-active an EOL
branch of bitbake.

Jan

-- 
Siemens AG, Technology
Competence Center Embedded Linux