From: Anton Mikanovich <amikan@ilbers.de>
To: Jan Kiszka <jan.kiszka@siemens.com>,
isar-users <isar-users@googlegroups.com>,
Baurzhan Ismagulov <ibr@ilbers.de>
Subject: Re: Error logging broken with next?
Date: Tue, 17 May 2022 16:42:13 +0300 [thread overview]
Message-ID: <d5f0e100-6e14-cda1-b540-34c5267a0572@ilbers.de> (raw)
In-Reply-To: <3ddcda7f-41ba-5e25-3ec8-959a5ff356cc@ilbers.de>
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)
next prev parent reply other threads:[~2022-05-17 13:42 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-13 16:49 Jan Kiszka
2022-05-16 7:49 ` Baurzhan Ismagulov
2022-05-16 11:05 ` Jan Kiszka
2022-05-17 12:35 ` Anton Mikanovich
2022-05-17 13:42 ` Anton Mikanovich [this message]
2022-05-19 6:01 ` Jan Kiszka
2022-05-23 19:06 ` Jan Kiszka
2022-05-24 7:43 ` Anton Mikanovich
2022-05-24 14:23 ` Anton Mikanovich
2022-05-24 15:54 ` Jan Kiszka
2022-05-24 15:57 ` Jan Kiszka
2022-05-24 16:05 ` Anton Mikanovich
2022-05-24 16:07 ` Jan Kiszka
2022-05-24 16:14 ` Anton Mikanovich
2022-05-24 16:36 ` Jan Kiszka
2022-05-24 19:50 ` Anton Mikanovich
2022-05-25 5:30 ` Anton Mikanovich
2022-05-25 6:40 ` Jan Kiszka
2022-05-24 16:02 ` 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=d5f0e100-6e14-cda1-b540-34c5267a0572@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