Re: Project isar_claudius_ilbers_fast_ci on isar-build.org

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

On 25.04.19 12:24, Claudius Heine wrote:
> Hi Jan,
> 
> On 25/04/2019 12.19, Jan Kiszka wrote:
>> On 25.04.19 11:50, Maxim Yu. Osipov wrote:
>>> Hi Claudius,
>>>
>>> I've created and configured the project Project isar_claudius_ilbers_fast_ci 
>>> to launch "fast" CI.
>>>
>>> I've started the test build in this project (it clones your branch 
>>> ch/ilbers-ci from https://github.com/cmhe/isar)and it immediately reproduced 
>>> the error I reported before:
>>>
>>> http://isar-build.org:8080/job/isar_claudius_ilbers_fast_ci/1/console
>>>
>>> Any problems with access,
>>> please let me know.
>>
>> In fact, it didn't even need that complication in the first place: The issue 
>> is also reproducible in our gitlab-ci environment.
>>
>> Claudius, you have access to it, and you can look into the logs what went 
>> wrong or push new versions there. It just takes a few minutes to get results 
>> as the failure is early.
>>
>> Once we understood this issue, it would also be good to understand why 
>> Claudius earlier run on the jenkins CI didn't reveal it. But one after the other.
> 
> Well probably because "fast" enabled cross-compilation.
> 
> 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. So we have a race that probably papers over 
it in larger CI runs. If you can reproduce without that race, please debug.

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

Jan

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