From: Anton Mikanovich <amikan@ilbers.de>
To: Jan Kiszka <jan.kiszka@siemens.com>,
isar-users <isar-users@googlegroups.com>
Cc: Baurzhan Ismagulov <ibr@ilbers.de>
Subject: Re: Error logging broken with next?
Date: Tue, 24 May 2022 19:02:42 +0300 [thread overview]
Message-ID: <9993384f-55a7-dd5f-675a-d82c1f91ad3f@ilbers.de> (raw)
In-Reply-To: <2be1421c-b534-c5c7-cf5e-1510cc3c81a5@siemens.com>
24.05.2022 18:54, Jan Kiszka wrote:
> Ok, then the environment of the glibc case is not the same as our for
> the dpkg_runbuild. The latter is broken, and we need to understand how
> to restore its output in Isar - very likely not in bitbake.
>
> Jan
>
This is not about the environment, but because the task is in python and
bash
part is executed with bb.build.exec_func API. You can easily test it in
Yocto
with the following example:
test_fun() {
echo "FAIL!"
false
}
python do_test() {
bb.build.exec_func("test_fun", d)
}
addtask test
$ bitbake -c do_test recipename
prev parent reply other threads:[~2022-05-24 16:02 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
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 [this message]
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=9993384f-55a7-dd5f-675a-d82c1f91ad3f@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