From: "Maxim Yu. Osipov" <mosipov@ilbers.de>
To: isar-users@googlegroups.com
Subject: [PATCH 1/2] ci_build: Include de0-nano-soc into parallel fast build
Date: Sat, 18 May 2019 13:11:57 +0200 [thread overview]
Message-ID: <20190518111158.16539-1-mosipov@ilbers.de> (raw)
Signed-off-by: Maxim Yu. Osipov <mosipov@ilbers.de>
---
scripts/ci_build.sh | 6 +-----
1 file changed, 1 insertion(+), 5 deletions(-)
diff --git a/scripts/ci_build.sh b/scripts/ci_build.sh
index a38e2b7..ae9f5c9 100755
--- a/scripts/ci_build.sh
+++ b/scripts/ci_build.sh
@@ -86,6 +86,7 @@ do
multiconfig:qemuarm-buster:isar-image-base \
multiconfig:qemuarm64-stretch:isar-image-base \
multiconfig:qemuamd64-stretch:isar-image-base \
+ multiconfig:de0-nano-soc-stretch:isar-image-base \
multiconfig:rpi-stretch:isar-image-base"
;;
-q|--quiet)
@@ -124,13 +125,8 @@ fi
# Start build for the defined set of configurations
bitbake $BB_ARGS $TARGETS_SET
-# Note: de0-nano-soc build is launched separately as
-# parallel build with the same target arch (armhf) fails.
-# The problem is being investigated
# In addition test SDK creation
if [ -n "$FAST_BUILD" ]; then
- bitbake $BB_ARGS multiconfig:de0-nano-soc-stretch:isar-image-base
- while [ -e bitbake.sock ]; do sleep 1; done
bitbake $BB_ARGS -c do_populate_sdk multiconfig:qemuarm-stretch:isar-image-base
fi
--
2.11.0
next reply other threads:[~2019-05-18 11:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-18 11:11 Maxim Yu. Osipov [this message]
2019-05-18 11:11 ` [PATCH 2/2] ci_build: Introduce REPRO_TARGETS_SET Maxim Yu. Osipov
2019-05-20 13:48 ` Maxim Yu. Osipov
2019-05-23 12:27 ` Claudius Heine
2019-05-23 12:34 ` Maxim Yu. Osipov
2019-05-23 12:38 ` Claudius Heine
2019-05-23 12:46 ` Maxim Yu. Osipov
2019-05-23 13:17 ` Claudius Heine
2019-05-20 13:47 ` [PATCH 1/2] ci_build: Include de0-nano-soc into parallel fast build Maxim Yu. Osipov
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=20190518111158.16539-1-mosipov@ilbers.de \
--to=mosipov@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