From: Jan Kiszka <jan.kiszka@siemens.com>
To: Baurzhan Ismagulov <ibr@radix50.net>, isar-users@googlegroups.com
Subject: Re: [PATCH] scripts/ci_build.sh: Don't fail on bullseye build errors
Date: Mon, 22 Jun 2020 09:39:04 +0200 [thread overview]
Message-ID: <c5b0e32f-1dd7-abc1-680d-7ca6ffd219bd@siemens.com> (raw)
In-Reply-To: <20200621200843.23865-1-ibr@radix50.net>
On 21.06.20 22:08, Baurzhan Ismagulov wrote:
> From: Baurzhan Ismagulov <ibr@ilbers.de>
>
> Bullseye targets fail to build with the following error message:
>
> ERROR: mc:qemuarm-bullseye:libhello-0.1-98f2e41-r0 do_install_builddeps: Execution of '/workspace/build/isar_master/447/build/tmp/work/debian-bullseye-armhf/libhello/0.1-98f2e41-r0/temp/run.do_install_builddeps.29112' failed with exit code 2:
> ...
> dpkg-checkbuilddeps: error: Unmet build dependencies: build-essential:native
>
> Workaround: If bullseye doesn't build, print a message but not mark the
> build as failed.
>
I'm carrying a disabling patch for bullseye in my queue as well.
There are two issues, in fact. The bigger one is the above. The smaller
one is that cowsay needs a refreshment to build again, but only for
bullseye.
Jan
> Signed-off-by: Vlad Serebrennikov <vserebr@ilbers.de>
> Signed-off-by: Baurzhan Ismagulov <ibr@ilbers.de>
> ---
> scripts/ci_build.sh | 29 ++++++++++++++++++++++++-----
> 1 file changed, 24 insertions(+), 5 deletions(-)
>
> diff --git a/scripts/ci_build.sh b/scripts/ci_build.sh
> index adc403b..d2c707b 100755
> --- a/scripts/ci_build.sh
> +++ b/scripts/ci_build.sh
> @@ -22,33 +22,39 @@ BB_ARGS="-v"
> TARGETS_SET="\
> mc:qemuarm-stretch:isar-image-base \
> mc:qemuarm-buster:isar-image-base \
> - mc:qemuarm-bullseye:isar-image-base \
> mc:qemuarm64-stretch:isar-image-base \
> mc:qemui386-stretch:isar-image-base \
> mc:qemui386-buster:isar-image-base \
> - mc:qemui386-bullseye:isar-image-base \
> mc:qemuamd64-stretch:isar-image-base \
> mc:qemuamd64-buster:isar-image-base \
> mc:qemuamd64-buster-tgz:isar-image-base \
> - mc:qemuamd64-bullseye:isar-image-base \
> mc:qemumipsel-stretch:isar-image-base \
> mc:qemumipsel-buster:isar-image-base \
> - mc:qemumipsel-bullseye:isar-image-base \
> mc:nand-ubi-demo-buster:isar-image-ubi \
> mc:rpi-stretch:isar-image-base"
> # qemu-user-static of <= buster too old to build that
> # mc:qemuarm64-buster:isar-image-base
> # mc:qemuarm64-bullseye:isar-image-base
>
> +TARGETS_SET_BULLSEYE="\
> + mc:qemuamd64-bullseye:isar-image-base \
> + mc:qemuarm-bullseye:isar-image-base \
> + mc:qemui386-bullseye:isar-image-base \
> + mc:qemumipsel-bullseye:isar-image-base \
> +"
> +
> CROSS_TARGETS_SET="\
> mc:qemuarm-stretch:isar-image-base \
> mc:qemuarm-buster:isar-image-base \
> - mc:qemuarm-bullseye:isar-image-base \
> mc:qemuarm64-stretch:isar-image-base \
> mc:qemuamd64-stretch:isar-image-base \
> mc:de0-nano-soc-stretch:isar-image-base \
> mc:rpi-stretch:isar-image-base"
>
> +CROSS_TARGETS_SET_BULLSEYE="\
> + mc:qemuarm-bullseye:isar-image-base \
> +"
> +
> REPRO_TARGETS_SET_SIGNED="\
> mc:de0-nano-soc-stretch:isar-image-base \
> mc:qemuarm64-stretch:isar-image-base"
> @@ -176,6 +182,11 @@ fi
> sed -i -e 's/ISAR_CROSS_COMPILE ?= "0"/ISAR_CROSS_COMPILE ?= "1"/g' conf/local.conf
> bitbake $BB_ARGS $CROSS_TARGETS_SET
> while [ -e bitbake.sock ]; do sleep 1; done
> +if bitbake $BB_ARGS $CROSS_TARGETS_SET_BULLSEYE; then
> + echo "bullseye cross: PASSED"
> +else
> + echo "bullseye cross: KFAIL"
> +fi
> # In addition test SDK creation
> bitbake $BB_ARGS -c do_populate_sdk mc:qemuarm-stretch:isar-image-base
> while [ -e bitbake.sock ]; do sleep 1; done
> @@ -185,6 +196,14 @@ if [ -z "$FAST_BUILD" ]; then
> sudo rm -rf tmp
> sed -i -e 's/ISAR_CROSS_COMPILE ?= "1"/ISAR_CROSS_COMPILE ?= "0"/g' conf/local.conf
> bitbake $BB_ARGS $TARGETS_SET
> + while [ -e bitbake.sock ]; do sleep 1; done
> +
> + if bitbake $BB_ARGS $TARGETS_SET_BULLSEYE; then
> + echo "bullseye: PASSED"
> + else
> + echo "bullseye: KFAIL"
> + fi
> + while [ -e bitbake.sock ]; do sleep 1; done
> fi
>
> cp -a "${ISARROOT}/meta/classes/dpkg-base.bbclass" "${ISARROOT}/meta/classes/dpkg-base.bbclass.ci-backup"
>
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2020-06-22 7:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-21 20:08 Baurzhan Ismagulov
2020-06-22 7:39 ` Jan Kiszka [this message]
2020-07-30 16:09 ` Baurzhan Ismagulov
2020-08-11 7:01 ` Jan Kiszka
2020-06-22 10:42 ` Henning Schild
2020-07-30 16:08 ` Baurzhan Ismagulov
2020-08-18 11:23 ` Henning Schild
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=c5b0e32f-1dd7-abc1-680d-7ca6ffd219bd@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=ibr@radix50.net \
--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