Re: [PATCH] isar-bootstrap: Fix and cleanup bind mounting

[Jan Kiszka <jan.kiszka@siemens.com>]

On 04.12.18 11:49, Maxim Yu. Osipov wrote:
> On 12/3/18 3:59 PM, Jan Kiszka wrote:
>> On 30.11.18 10:20, Maxim Yu. Osipov wrote:
>>> Hi Jan,
>>>
>>> I've just tried this patch (on the 'next' with reverted patch d40a9ac0) and 
>>> ran "fast" CI
>>>
>>> isar$mount | wc -l
>>> 34
>>>
>>> isar$./scripts/ci_build.sh -q -f
>>>
>>> CI script hung on CI stage when dpkg-base is modified
>>> causing rebuilding recipes based on dpkg-base.
>>>
>>> The mount reports less (!) mount points than before launching the script.
>>>
>>> mount | wc -l
>>> 31
>>
>> Any news on what's different on your side? Where exactly does your build hang? 
>> Was your CI environment in a clean state when running this test? Before the 
>> comment lots of things leaked.
> 
> 
> On my stretch laptop (i7-6820HQ CPU @ 2.70GHz (8 cores) with SSD)  the reported 
> problem is reproducible (I rerun 'ci_build.sh -q -f' several times in clean 
> state) it hung and with the less mount points (the mount points before and after 
> running are attached).
> 
> The strange thing that I observe two bitbake processes:
> 
> myo      26373  0.0  0.3 153116 29732 pts/0    Sl+  12:31   0:01 python3 
> /home/myo/work/isar/src/trunk/isar/bitbake/bin/bitbake 
> multiconfig:qemuarm-stretch:isar-image-base 
> multiconfig:qemuarm64-stretch:isar-image-base 
> multiconfig:qemuamd64-stretch:isar-image-base
> 
> myo      26379  2.5  0.6 328476 50028 ?        Sl   12:31   0:40 python3 
> /home/myo/work/isar/src/trunk/isar/bitbake/bin/bitbake 
> multiconfig:qemuarm-stretch:isar-image-base 
> multiconfig:qemuarm64-stretch:isar-image-base 
> multiconfig:qemuamd64-stretch:isar-image-base
> 

We run multiple bitbake sessions after each other. Maybe the first one never 
terminates (get stuck), and that is also why the rm after the first session 
fails. You need to stop the build there and analyse what is keeping the mount 
points busy.

> 
> When I turned on verbosity (called ci_build.sh without '-q' switch)
> 'scripts/ci_build -f' succeeded.
> 
> Build also fails on isar-build.org
> http://isar-build.org:8080/job/isar_mosipov_next/98/console:
> it complains  on
> 'rm: cannot remove 
> '/workspace/build/isar_mosipov_next/98/build/tmp/work/debian-stretch-armhf/isar-bootstrap-target/rootfs/dev': 
> Device or resource busy'
> 
> Note that ci-build.sh on isar-build.org is also called with '-q' switch.
> 
> 
> Questions:
> 
> 1) Did you launch ci_build with '-q' option?
> 

yes

> 2) Did you inspect mount points before and after launching ci_build? Are they 
> identical?
> 

yes

> 3) Do you run this in docker?
> 

yes, in all setups.

Jan

-- 
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux