From: Baurzhan Ismagulov <ibr@radix50.net>
To: isar-users <isar-users@googlegroups.com>
Subject: Re: Project isar_claudius_ilbers_fast_ci on isar-build.org
Date: Thu, 25 Apr 2019 12:54:33 +0200 [thread overview]
Message-ID: <20190425105433.GK21981@yssyq.m.ilbers.de> (raw)
In-Reply-To: <bc7af3f9-21bc-339e-fb31-ab53c0fcacaf@siemens.com>
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?
> 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.
> > 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.
With kind regards,
Baurzhan.
next prev parent reply other threads:[~2019-04-25 10:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-25 9:50 Maxim Yu. Osipov
2019-04-25 10:19 ` Jan Kiszka
2019-04-25 10:24 ` Claudius Heine
2019-04-25 10:30 ` Jan Kiszka
2019-04-25 10:54 ` Baurzhan Ismagulov [this message]
2019-04-25 10:58 ` Jan Kiszka
2019-04-25 11:04 ` Baurzhan Ismagulov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190425105433.GK21981@yssyq.m.ilbers.de \
--to=ibr@radix50.net \
--cc=isar-users@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox