Re: [PATCH v5 0/5] UBI support

[Claudius Heine <claudius.heine.ext@siemens.com>]

Hi Maxim,

On 13/02/2019 09.36, Maxim Yu. Osipov wrote:
> Hi Claudius,
> 
> You can easily access the build directory with all build artifacts of 
> the last build (the build artifacts of previous builds are wiped out 
> except logs): Just go to
> 
> http://isar-build.org:8080/job/isar_mosipov_next/ws/build.
> 
> FYI: The last (#141) build (with your patches (Click on Changes)) failed:
> 
> See:
> http://isar-build.org:8080/job/isar_mosipov_next/141/console
> 
> The previous (#140) (actually is the same as 'next') is OK:
> 
> http://isar-build.org:8080/job/isar_mosipov_next/140/console

Thx!

> 
> 
> Just to doublecheck: have you tried on your local PC
> './scripts/ci_build.sh -q'?

Well the internal gitlab ci runs ./scripts/ci_build.sh -q -f
On my machine I normally just run single builds.

I now started ci_build.sh -q on my local machine could produce an error:

Log data follows:
| DEBUG: Executing shell function do_build
| Ign file: isar InRelease
| Ign file: isar Release.gpg
| Ign file: isar Release
| Err file: isar/main armhf Packages
|   File not found
| Ign file: isar/main Translation-en
| W: Failed to fetch 
file:/isar-apt/dists/isar/main/binary-armhf/Packages  File not found
|
| E: Some index files failed to download. They have been ignored, or old 
ones used instead.
| WARNING: 
/mnt/data/isar/layers/isar-master/build/tmp/work/debian-jessie-armhf/buildchroot-target/temp/run.do_build.23502:1 
exit 100 from 'sudo -E chroot "$ROOTFSDIR" /usr/bin/apt-get update -o 
Dir::Etc::sourcelist="sources.list.d/isar-apt.list" -o 
Dir::Etc::sourceparts="-" -o APT::Get::List-Cleanup="0"'
| ERROR: Function failed: do_build (log file is located at 
/mnt/data/isar/layers/isar-master/build/tmp/work/debian-jessie-armhf/buildchroot-target/temp/log.do_build.23502)

I suspect that this has nothing to do with that patchset directly, I 
rather think that this issue was there before, but because I added an 
additional task the execution order changed slightly and we now we run 
into that race condition under some conditions.

I don't think that this will be an easy or quick fix. But I will 
investigate that.

regards,
Claudius

> 
> Regards,
> Maxim.
> 
> On 2/12/19 5:36 PM, Claudius Heine wrote:
>> On 12/02/2019 16.51, [ext] Claudius Heine wrote:
>>> Hi Maxim,
>>>
>>> On 12/02/2019 15.06, Maxim Yu. Osipov wrote:
>>>> Hi again, Claudius,
>>>>
>>>> I've applied "[PATCH v2 1/1] meta: added do_transform_template task 
>>>> as templating system and switch" before UBI support v5 series
>>>> and CI failed:
>>>>
>>>> See for details
>>>>
>>>> http://isar-build.org:8080/job/isar_mosipov_next/139/console
>>>
>>> I only see errors that complain about code that is not affected by 
>>> the template and ubi patchset. It complains about the 
>>> 'buildchroot-target', which does not use the ubi classes or the 
>>> template functions.
>>>
>>> I will investigate further, but currently I don't think that the bug 
>>> is in those patchesets that lead to this issue. Currently I cannot 
>>> reproduce this issue on my host.
>>
>> I tried reproducing it on the siemens internal ci server without 
>> success. So if that issue persists on your CI then I would need access 
>> to that server to debug that issue or maybe the dump of the bitbake 
>> environment for the buildchroot-target task + the state of the tmp 
>> directory.
>>
>> Regards,
>> Claudius
>>
> 
> 

-- 
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