From: Baurzhan Ismagulov <ibr@radix50.net>
To: isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH v4 00/11] Support for building TF-A and OP-TEE, add STM32MP15x board
Date: Wed, 25 Nov 2020 19:58:02 +0100 [thread overview]
Message-ID: <20201125185802.GV31950@yssyq.m.ilbers.de> (raw)
In-Reply-To: <f407d516-937d-70dc-4123-bed3fd05135a@siemens.com>
On Wed, Nov 25, 2020 at 06:47:50AM +0100, Jan Kiszka wrote:
> > Looks good to me, has just failed on CI due to python3. I'll test on top of the
> > python3 fix and let you know.
>
> How comes that? The new python bits of this series should only be
> executed inside the buildchroot. Do you have a pointer to the failing build?
http://ci.isar-build.org:8080/job/isar_am_devel_fast/28/consoleFull
ERROR: mc:stm32mp15x-buster:isar-image-base-1.0-r0 do_wic_image: Execution of '/workspace/build/isar_am_devel_fast/28/build/tmp/work/debian-buster-armhf/isar-image-base-stm32mp15x-wic-img/1.0-r0/temp/run.do_wic_image.27755' failed with exit code 1:
/usr/bin/ln: failed to create symbolic link '/usr/bin/python3-native/python3': File exists
INFO: Creating image(s)...
ERROR: A native program /usr/bin/python3-native/python3 required to build the image was not found (see details above).
Wic failed to find a recipe to build native /usr/bin/python3-native/python3. Please file a bug against wic.
mv: cannot stat '/workspace/build/isar_am_devel_fast/28/build/tmp/deploy/buildchroot-target/debian-buster-armhf/tmp/tmp.W51km1H9Cv/isar-image-base-debian-buster-stm32mp15x.wic/stm32mp15x-202011231326-sda.direct.bmap': No such file or directory
WARNING: exit code 1 from a shell command.
ERROR: Logfile of failure stored in: /workspace/build/isar_am_devel_fast/28/build/tmp/work/debian-buster-armhf/isar-image-base-stm32mp15x-wic-img/1.0-r0/temp/log.do_wic_image.27755
If that is a race, then it could be triggered by any irrelevant change. With
the python3 patch applied, the CI has passed. I'm ready to apply the series,
please let me know whether you see any issues.
With kind regards,
Baurzhan.
next prev parent reply other threads:[~2020-11-25 18:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-23 7:53 Jan Kiszka
2020-11-23 7:53 ` [PATCH v4 01/11] meta-isar: Lift de0-nano-soc build to buster Jan Kiszka
2020-11-23 7:53 ` [PATCH v4 02/11] meta-isar: linux-mainline: Update to latest 5.4.70 Jan Kiszka
2020-11-23 7:53 ` [PATCH v4 03/11] meta-isar: u-boot: Update to 2020.10 Jan Kiszka
2020-11-23 7:53 ` [PATCH v4 04/11] meta-isar: u-boot: Factor our de0-nano-soc recipe Jan Kiszka
2020-11-23 7:53 ` [PATCH v4 05/11] meta-isar: example-raw: Purge securetty from target image Jan Kiszka
2020-11-23 7:53 ` [PATCH v4 06/11] Add STM32MP15x eval board Jan Kiszka
2020-11-23 7:53 ` [PATCH v4 07/11] Add recipe include for building custom Trusted Firmware A Jan Kiszka
2020-11-23 7:53 ` [PATCH v4 08/11] stm32mp15x: Switch to TF-A based boot Jan Kiszka
2020-11-23 7:53 ` [PATCH v4 09/11] Add recipe include for building custom OP-TEE Jan Kiszka
2020-11-23 7:53 ` [PATCH v4 10/11] meta-isar: u-boot-stm32mp15x: Add patches needed for OP-TEE usage Jan Kiszka
2020-11-23 7:53 ` [PATCH v4 11/11] meta-isar: Add OP-TEE to STM32MP15x board Jan Kiszka
2020-11-24 16:52 ` [PATCH v4 00/11] Support for building TF-A and OP-TEE, add " Baurzhan Ismagulov
2020-11-25 5:47 ` Jan Kiszka
2020-11-25 18:58 ` Baurzhan Ismagulov [this message]
2020-11-25 20:30 ` Jan Kiszka
2020-11-26 15:54 ` 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=20201125185802.GV31950@yssyq.m.ilbers.de \
--to=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