Re: [PATCH v2 0/9] Add support for automatic partial rebuilds on recipe changes

[Alexander Smirnov <asmirnov@ilbers.de>]

[-- Attachment #1: Type: text/plain, Size: 2071 bytes --]

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?

Alex

[-- Attachment #2: log.txt --]
[-- Type: text/plain, Size: 3183 bytes --]

builder@zbook:~/isar$ cat /home/builder/isar/build/tmp/work/debian-stretch-armhf/example-hello-0.2-86cc719-r0/temp/log.do_build.21911
DEBUG: Executing shell function do_build
Get:1 file:/isar-apt isar InRelease
Ign:1 file:/isar-apt isar InRelease
Get:2 file:/isar-apt isar Release [2,861 B]
Get:2 file:/isar-apt isar Release [2,861 B]
Get:3 file:/isar-apt isar Release.gpg
Ign:3 file:/isar-apt isar Release.gpg
Reading package lists...
W: The repository 'file:/isar-apt isar Release' is not signed.
hostname: Name or service not known
dh_testdir
dh_testroot
dh_prep
dh_testdir
dh_testroot
dh_install
dh_install: Compatibility levels before 9 are deprecated (level 7 in use)
dh_installdocs
dh_installdocs: Compatibility levels before 9 are deprecated (level 7 in use)
dh_installchangelogs
dh_compress
dh_fixperms
dh_installdeb
dh_installdeb: Compatibility levels before 9 are deprecated (level 7 in use)
dh_gencontrol
dh_md5sums
dh_builddeb
dpkg-deb: building package 'hello-build-deps' in '../hello-build-deps_0.2_all.deb'.

The package has been created.
Attention, the package has been created in the current directory,
not in ".." as indicated by the message above!
Selecting previously unselected package hello-build-deps.
(Reading database ... 15754 files and directories currently installed.)
Preparing to unpack hello-build-deps_0.2_all.deb ...
Unpacking hello-build-deps (0.2) ...
Reading package lists...
Building dependency tree...
Reading state information...
Correcting dependencies...Starting pkgProblemResolver with broken count: 1
Starting 2 pkgProblemResolver with broken count: 1
Investigating (0) hello-build-deps:armhf < 0.2 @iU mK Nb Ib >
Broken hello-build-deps:armhf Depends on libhello-dev:armhf < none @un H >
  Removing hello-build-deps:armhf because I can't find libhello-dev:armhf
Done
 Done
Starting pkgProblemResolver with broken count: 0
Starting 2 pkgProblemResolver with broken count: 0
Done
The following packages will be REMOVED:
  hello-build-deps
0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 9,216 B disk space will be freed.
E: Can not write log (Is /dev/pts mounted?) - posix_openpt (19: No such device)
(Reading database ... 15758 files and directories currently installed.)
Removing hello-build-deps (0.2) ...
mk-build-deps: Unable to install hello-build-deps at /usr/bin/mk-build-deps line 402.
mk-build-deps: Unable to install all build-dep packages
dpkg-buildpackage: info: source package hello
dpkg-buildpackage: info: source version 0.2
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Alexander Smirnov <asmirnov@ilbers.de>
 dpkg-source --before-build git
dpkg-buildpackage: info: host architecture armhf
dpkg-checkbuilddeps: error: Unmet build dependencies: libhello-dev
dpkg-buildpackage: warning: build dependencies/conflicts unsatisfied; aborting
dpkg-buildpackage: warning: (Use -d flag to override.)
WARNING: exit code 3 from a shell command.
ERROR: Function failed: do_build (log file is located at /home/builder/isar/build/tmp/work/debian-stretch-armhf/example-hello-0.2-86cc719-r0/temp/log.do_build.21911)