Re: Error logging broken with next?

[Anton Mikanovich <amikan@ilbers.de>]

24.05.2022 19:07, Jan Kiszka wrote:
> On 24.05.22 18:05, Anton Mikanovich wrote:
>> 24.05.2022 18:57, Jan Kiszka wrote:
>>> Just thinking loudly: Is it our try-finally that changes the output
>>> trigger for knotty?
>>>
>>>       try:
>>>           bb.build.exec_func("dpkg_runbuild", d)
>>>       finally:
>>>           bb.build.exec_func("dpkg_undo_mounts", d)
>>>           bb.utils.unlockfile(lock)
>>>
>>> Jan
>>>
>> No, this is not because of try-finally itself, but because of exec_func
>> API.
>> Look at my previous mail.
>>
> But that is just the same with glibc, and that worked fine in poky
> during my test yesterday, ie. produced the correct dump.
>
> Jan
>
No, in "glibc" example failed code is executed from the bash task.
And bb.build.exec_func is python API called from python task.
This is not the same.

As I previously said, there is no difference between Yocto and Isar:
1) fail in bash task generates full log
2) fail in bash code called from python task generates masked log

Please try do_test example from one of the previous mails on Yocto.