Re: Error logging broken with next?

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

On 17.05.22 15:42, Anton Mikanovich wrote:
> 17.05.2022 15:35, Anton Mikanovich wrote:
>> 13.05.2022 19:49, Jan Kiszka wrote:
>>> Hi,
>>>
>>> I vaguely recall that you, Baurzhan, told me that logs of failing tasks
>>> are not always dumped, right? I'm on current next now, building breaking
>>> kernels, and all I get now is our useless python backtrace, always. All
>>> is fine with log.do_dpkg_build, though. Is that the issue? Very annoying
>>> and a no-go for CI. No time to bisect ATM, unfortunately.
>>>
>>> Jan
>>>
>> Hello,
>>
>> Thanks for reporting.
>> I've reproduced the issue on the latest next and also see the full log
>> is still there on v0.8
>> Will try to bisect to find the reason (bitbake update?).
>>
> So, that's all about
> https://github.com/openembedded/bitbake/commit/cf864cd84172f605b0e1777c3defc000fa3a7379
> 
> (included in bitbake 1.50.4)
> 

So, already "bitbake ... | cat" causes this issue? Is there any command
line option that avoids this? I wonder what kas could do here without
breaking older versions. And why no one reported this so far from kas'
OE community.

Jan

-- 
Siemens AG, Technology
Competence Center Embedded Linux