Re: Error logging broken with next?

[Baurzhan Ismagulov <ibr@radix50.net>]

On Fri, May 13, 2022 at 06:49:37PM +0200, Jan Kiszka wrote:
> 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.

Can you provide some details for reproducing? Failure during make, or failure
in the recipe?

If you are running ci_build.sh -d, the complete bitbake output should be
visible in stdout.

If you are running ci_build.sh without -d, only a brief testcase list (1/23
repro pass) is shown for passing testcases. For failing testcases, stderr is
dumped. One issue here is that bitbake captures stderr of its children and
prints that to stdout, by design
(https://lists.openembedded.org/g/bitbake-devel/message/13640). We are
evaluating dumping bitbake stdout + stderr in this case.

With kind regards,
Baurzhan.