From: Jan Kiszka <jan.kiszka@siemens.com>
To: Alexander Smirnov <asmirnov@ilbers.de>,
isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH v2 0/9] Add support for automatic partial rebuilds on recipe changes
Date: Wed, 14 Feb 2018 14:10:20 +0100 [thread overview]
Message-ID: <ad6449b9-018e-fcc7-1a38-2d6beeb0cbb3@siemens.com> (raw)
In-Reply-To: <01a34333-06a2-4df0-a51e-17aced9f9ee3@ilbers.de>
On 2018-02-14 13:57, Alexander Smirnov wrote:
> On 02/14/2018 03:41 PM, Jan Kiszka wrote:
>> On 2018-02-14 12:33, Alexander Smirnov wrote:
>>> On 02/13/2018 11:05 PM, Jan Kiszka wrote:
>>>> Yeah, finally Yocto/OE-like usability: This ensures for many cases that
>>>> changes to recipes lead to rebuilds of dependent recipes, including the
>>>> final image. Some extra measures are needed so that those rebuilds work
>>>> with clean dirs.
>>>>
>>>> And if the change detection should not work, e.g. changes to file://
>>>> resources are not detected, then a clean or cleanall task is now
>>>> available and ensures a proper manual rebuild.
>>>>
>>>> This massively increases the fun factor when developing Isar projects.
>>>
>>>
>>> Wow, just noticed that with this series bitbake has started to run tasks
>>> in parallel.. How it's working? :-)
>>>
>>>
>>> Currently 4 running tasks (54 of 217) 24%
>>> |########################################
>>> |
>>> 0: mc:rpi-jessie:buildchroot-1.0-r0 do_build - 101s (pid 3271)
>>> 1: mc:qemui386-stretch:buildchroot-1.0-r0 do_build - 101s (pid 3336)
>>> 2: mc:qemui386-jessie:buildchroot-1.0-r0 do_build - 100s (pid 3457)
>>> 3: mc:qemuarm-wheezy:buildchroot-1.0-r0 do_build - 100s (pid 3524)
>>
>> Didn't notice that this wasn't the case before (most of my workload had
>> linear ordering), but I could imagine that the lacking signatures forced
>> bitbake to serialize. Just guessing.
>>
>
> There is still the same build problem as reported yesterday, log is
> attached. Dropping patch #3 fixes it.
>
> Line I used to build:
>
> $ time bitbake multiconfig:qemuarm-wheezy:isar-image-base
> multiconfig:qemuarm-jessie:isar-image-base
> multiconfig:qemuarm-stretch:isar-image-base
> multiconfig:qemui386-jessie:isar-image-base
> multiconfig:qemui386-stretch:isar-image-base
> multiconfig:qemuamd64-jessie:isar-image-base
> multiconfig:qemuamd64-stretch:isar-image-base
> multiconfig:rpi-jessie:isar-image-base
>
> Just for sure stated build in CI server:
> http://isar-build.org:8080/job/isar_asmirnov_devel/8/console
>
> Also failed. Could I dropped this patch from the series?
Not before you can explain why things fail and why that patch causes
this. We need to understand the problem. Let me reproduce...
Jan
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2018-02-14 13:10 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-13 20:05 Jan Kiszka
2018-02-13 20:05 ` [PATCH v2 1/9] dpkg-raw: Install hooks automatically Jan Kiszka
2018-02-13 20:05 ` [PATCH v2 2/9] Fix indention of base_do_build Jan Kiszka
2018-02-13 20:05 ` [PATCH v2 3/9] Add clean and cleanall tasks Jan Kiszka
2018-02-14 15:14 ` [PATCH v3 " Jan Kiszka
2018-02-13 20:05 ` [PATCH v2 4/9] Enable recipe caching Jan Kiszka
2018-02-13 20:05 ` [PATCH v2 5/9] Move buildchroot mounts into dpkg-base class Jan Kiszka
2018-02-13 20:17 ` Alexander Smirnov
2018-02-13 20:47 ` Jan Kiszka
2018-02-14 5:54 ` Alexander Smirnov
2018-02-14 8:37 ` Jan Kiszka
2018-02-14 8:52 ` [PATCH v3 " Jan Kiszka
2018-02-14 9:09 ` Alexander Smirnov
2018-02-14 9:16 ` Jan Kiszka
2018-02-13 20:05 ` [PATCH v2 6/9] Enable proper rebuilds on dependency changes Jan Kiszka
2018-02-13 20:05 ` [PATCH v2 7/9] dpkg-raw: Clean DEBIAN dir prior to filling it Jan Kiszka
2018-02-15 9:14 ` Claudius Heine
2018-02-15 9:18 ` Jan Kiszka
2018-02-15 10:26 ` Claudius Heine
2018-02-15 10:30 ` Alexander Smirnov
2018-02-15 10:53 ` [PATCH] dpkg-raw: Fix creation of DEBIAN folder Jan Kiszka
2018-02-15 15:39 ` Alexander Smirnov
2018-02-26 11:39 ` Andreas Reichel
2018-02-26 12:03 ` Jan Kiszka
2018-02-26 12:27 ` Andreas Reichel
2018-02-15 12:20 ` [PATCH v2 7/9] dpkg-raw: Clean DEBIAN dir prior to filling it Claudius Heine
2018-02-13 20:05 ` [PATCH v2 8/9] isar-image-base: Clean rootfs folder prior to building Jan Kiszka
2018-02-13 20:05 ` [PATCH v2 9/9] buildchroot: Clean up rootfs prior to populating it Jan Kiszka
2018-02-14 17:43 ` Alexander Smirnov
2018-02-14 17:48 ` Jan Kiszka
2018-02-14 11:33 ` [PATCH v2 0/9] Add support for automatic partial rebuilds on recipe changes Alexander Smirnov
2018-02-14 12:41 ` Jan Kiszka
2018-02-14 12:57 ` Alexander Smirnov
2018-02-14 13:10 ` Jan Kiszka [this message]
2018-02-14 13:29 ` Jan Kiszka
2018-02-14 13:38 ` Jan Kiszka
2018-02-14 13:49 ` Jan Kiszka
2018-02-14 14:06 ` Alexander Smirnov
2018-02-14 14:03 ` Alexander Smirnov
2018-02-14 14:10 ` Jan Kiszka
2018-02-14 17:51 ` Alexander Smirnov
2018-02-14 17:54 ` Jan Kiszka
2018-02-14 17:57 ` Alexander Smirnov
2018-02-14 18:02 ` Jan Kiszka
2018-02-14 18:34 ` Alexander Smirnov
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=ad6449b9-018e-fcc7-1a38-2d6beeb0cbb3@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=asmirnov@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