public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Claudius Heine <claudius.heine.ext@siemens.com>
To: "[ext] Henning Schild" <henning.schild@siemens.com>,
	"[ext] Jan Kiszka" <jan.kiszka@siemens.com>
Cc: "Maxim Yu. Osipov" <mosipov@ilbers.de>, isar-users@googlegroups.com
Subject: Re: [PATCH 3/4] ci: Include de0-nano-soc target into fast build
Date: Mon, 18 Feb 2019 11:29:59 +0100	[thread overview]
Message-ID: <940d2be5-9c73-e214-e8fa-6bb16616cbc2@siemens.com> (raw)
In-Reply-To: <20190218111849.6f56023c@md1za8fc.ad001.siemens.net>

Hi Henning,

On 18/02/2019 11.18, [ext] Henning Schild wrote:
> Am Fri, 15 Feb 2019 08:20:19 +0100
> schrieb "[ext] Jan Kiszka" <jan.kiszka@siemens.com>:
> 
>> On 14.02.19 17:08, Maxim Yu. Osipov wrote:
>>> Note: So far de0-nano-soc build is launched separately as
>>> parallel build with the same target arch (qemuarm) fails.
>>
>> jailhouse-images builds multiple images out of the same arch for
>> quite a while now. You may want to cross-check and adopt the patterns
>> there.
>>
>> Even if unrelated to this issue: A proper multiconfig file only
>> contains two assignments: MACHINE and DISTRO. This should be
>> eventually cleaned up in meta-isar so that user do not copy the wrong
>> patterns.
> 
> It is most likely false-sharing on multiconfig. Now if we look for
> "[stamp-extra-info]" in the source-tree we will find several
> combinations.
> 
> "${DISTRO}-${DISTRO_ARCH}"
> "${DISTRO}-${MACHINE}"
> "${MACHINE}-${DISTRO}"
> "${DISTRO}"
> 
> And possibly several tasks that should have an extra-stamp but do not.

Good point. That is also something that should be looked at before a 1.0 
release ;)

> Avoiding multiconfig is a very good idea, not just for CI ;).

I agree. Another way would be to set the tmp directory in the 
multiconfig like the bitbake manual documents:

https://www.yoctoproject.org/docs/latest/bitbake-user-manual/bitbake-user-manual.html#executing-a-multiple-configuration-build

regards,
Claudius

> 
> Henning
> 
>> Jan
>>
>>> While the problem with parallel build is being investigated
>>> de0-nano-soc build has to be checked by CI due to high
>>> importance.
>>>
>>> Signed-off-by: Maxim Yu. Osipov <mosipov@ilbers.de>
>>> ---
>>>    scripts/ci_build.sh | 7 +++++++
>>>    1 file changed, 7 insertions(+)
>>>
>>> diff --git a/scripts/ci_build.sh b/scripts/ci_build.sh
>>> index acce152..9c2322f 100755
>>> --- a/scripts/ci_build.sh
>>> +++ b/scripts/ci_build.sh
>>> @@ -126,6 +126,13 @@ 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
>>> +if [ -n "$FAST_BUILD" ]; then
>>> +    bitbake $BB_ARGS
>>> multiconfig:de0-nano-soc-stretch:isar-image-base +fi
>>> +
>>>    cp -a "${ISARROOT}/meta/classes/dpkg-base.bbclass"
>>> "${ISARROOT}/meta/classes/dpkg-base.bbclass.ci-backup" echo -e
>>> "do_fetch_append() {\n\n}" >>
>>> "${ISARROOT}/meta/classes/dpkg-base.bbclass"
>>
> 

-- 
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-54 Fax: (+49)-8142-66989-80 Email: ch@denx.de

  parent reply	other threads:[~2019-02-18 10:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-14 16:08 [PATCH 0/4] CI improvements Maxim Yu. Osipov
2019-02-14 16:08 ` [PATCH 1/4] ci: Introduce TARGETS_SET variable Maxim Yu. Osipov
2019-02-14 16:08 ` [PATCH 2/4] ci: Introduce --repro parameter to enable use of cached base repository Maxim Yu. Osipov
2019-02-14 16:08 ` [PATCH 3/4] ci: Include de0-nano-soc target into fast build Maxim Yu. Osipov
2019-02-15  7:20   ` Jan Kiszka
2019-02-18  8:59     ` Claudius Heine
2019-02-18 10:18     ` Henning Schild
2019-02-18 10:23       ` Jan Kiszka
2019-02-18 10:29       ` Claudius Heine [this message]
2019-02-14 16:08 ` [PATCH 4/4] ci: Disable use of cached base repository for fast build by default Maxim Yu. Osipov
2019-02-15 14:42 ` [PATCH 0/4] CI improvements 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=940d2be5-9c73-e214-e8fa-6bb16616cbc2@siemens.com \
    --to=claudius.heine.ext@siemens.com \
    --cc=henning.schild@siemens.com \
    --cc=isar-users@googlegroups.com \
    --cc=jan.kiszka@siemens.com \
    --cc=mosipov@ilbers.de \
    /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