From: Anton Mikanovich <amikan@ilbers.de>
To: isar-users@googlegroups.com
Cc: Anton Mikanovich <amikan@ilbers.de>
Subject: [PATCH] ci-build: Protect bullseye container with KFAIL
Date: Fri, 9 Apr 2021 11:15:20 +0300 [thread overview]
Message-ID: <20210409081520.399406-1-amikan@ilbers.de> (raw)
Bullseye building issue still not resolved, so container-bullseye fails
with error:
> fakeroot debian/rules clean
>semop(1): encountered an error: Function not implemented
This issue should be already fixed in host qemu/1:5.0-9 but we still
experience the same with qemu/1:5.2+dfsg-3~bpo10+1. Further research
will be done, so temporary fix for ci-build.sh introduced.
Bug report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965109
Signed-off-by: Anton Mikanovich <amikan@ilbers.de>
---
scripts/ci_build.sh | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/scripts/ci_build.sh b/scripts/ci_build.sh
index 6445b10..adc22e4 100755
--- a/scripts/ci_build.sh
+++ b/scripts/ci_build.sh
@@ -58,6 +58,9 @@ TARGETS_SET_BULLSEYE="\
TARGETS_CONTAINERS="\
mc:container-stretch:isar-image-base \
mc:container-buster:isar-image-base \
+"
+
+TARGETS_CONTAINERS_BULLSEYE="\
mc:container-bullseye:isar-image-base \
"
@@ -259,6 +262,12 @@ sed -i -e 's/\(IMAGE_INSTALL = .*\) example-module-${KERNEL_NAME}\(.*\)/\1\2/g'
sed -i -e 's/\(IMAGE_INSTALL = .*\) enable-fsck\(.*\)/\1\2/g' conf/local.conf
bitbake $BB_ARGS $TARGETS_CONTAINERS
while [ -e bitbake.sock ]; do sleep 1; done
+if bitbake $BB_ARGS $TARGETS_CONTAINERS_BULLSEYE; then
+ echo "bullseye container: PASSED"
+else
+ echo "bullseye container: KFAIL"
+fi
+while [ -e bitbake.sock ]; do sleep 1; done
# and SDK container image creation
echo 'SDK_FORMATS = "docker-archive"' >> conf/local.conf
bitbake $BB_ARGS -c do_populate_sdk mc:container-stretch:isar-image-base
--
2.20.1
next reply other threads:[~2021-04-09 8:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-09 8:15 Anton Mikanovich [this message]
[not found] ` <AM0PR10MB1939FA7325472104729E5ADC895F9@AM0PR10MB1939.EURPRD10.PROD.OUTLOOK.COM>
[not found] ` <982a11de-e990-5334-3896-2b96f7364715@ilbers.de>
2021-04-29 14:05 ` Moessbauer, Felix
2021-04-29 17:43 ` Henning Schild
[not found] ` <a4a7c550-ee88-2b3b-3f5b-20b0f32a1dfe@siemens.com>
2021-04-30 7:49 ` Moessbauer, Felix
2021-04-30 17:57 ` Jan Kiszka
2021-04-30 18:31 ` Jan Kiszka
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=20210409081520.399406-1-amikan@ilbers.de \
--to=amikan@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