Re: Project isar_claudius_ilbers_fast_ci on isar-build.org

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

On 25.04.19 12:54, Baurzhan Ismagulov wrote:
> On Thu, Apr 25, 2019 at 12:30:58PM +0200, Jan Kiszka wrote:
>>> Now I enabled cross-compilation for rpi-stretch locally and now I cannot
>>> build next there, but it builds apparently on isar-build...
>>
>> ...and apparently also on gitlab-ci.
> 
> Do I understand correctly, next does build on gitlab-ci?
> 

It's still running, but it seems to have past the failure points with Claudius' 
patches applied.

> 
>> So we have a race that probably papers
>> over it in larger CI runs. If you can reproduce without that race, please
>> debug.
> 
> That might also be a simpler issue like missing host packages. rpi requires
> some packages that are not required by other targets. If one doesn't usually
> build for rpi, those might be missing.
> 

There are multiple issues, only one of them is in the rpi target. There is 
generally no way around studying the logs in details.

> 
>>> I would really love to be able to reproduce exactly that issue locally...
>>
>> Then buy yourself a blade server as laptop ;). Look, not all issues can be
>> reproduced locally, at least not before you understood the boundary
>> conditions. That's very common and not always the problem of some CI system.
> 
> next should build locally. If there is a problem with the local build, we
> shouldn't ignore it. Maybe after this first problem is solved, one can also
> reproduce exactly that issue locally.

Let's understand the problems first, then do the post-portem analysis why there 
weren't found early if they could have.

Jan

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