public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: isar-users <isar-users@googlegroups.com>,
	Baurzhan Ismagulov <ibr@ilbers.de>
Subject: Error logging broken with next?
Date: Fri, 13 May 2022 18:49:37 +0200	[thread overview]
Message-ID: <75340600-5180-2f78-86f8-d5dc0c757a35@siemens.com> (raw)

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

-- 
Siemens AG, Technology
Competence Center Embedded Linux

             reply	other threads:[~2022-05-13 16:49 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-13 16:49 Jan Kiszka [this message]
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
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=75340600-5180-2f78-86f8-d5dc0c757a35@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=ibr@ilbers.de \
    --cc=isar-users@googlegroups.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