From: Jan Kiszka <jan.kiszka@siemens.com>
To: isar-users <isar-users@googlegroups.com>
Subject: Re: isar-bootstrap failures with debian-buster targets
Date: Fri, 23 Aug 2019 14:26:57 +0200 [thread overview]
Message-ID: <e4f22b4a-8f7b-183a-776a-4a9991a1db84@siemens.com> (raw)
In-Reply-To: <20190822152700.GB6062@yssyq.m.ilbers.de>
On 22.08.19 17:27, Baurzhan Ismagulov wrote:
> On Thu, Aug 22, 2019 at 05:00:42PM +0200, Jan Kiszka wrote:
>>> Is it reproducible with stock Isar?
>>
>> Yes, at least with next.
>>
>>>
>>> Is it reproducible outside of docker?
>>
>> No idea, I have no such environment.
>>
>> Interestingly, it does not trigger on our CI system running the exact same
>> docker image.
>
> I've tried building mc:qemuarm-stretch:i-i-b from next+ under
> kasproject/kas-isar:latest once, it succeeded. Once in how many times does it
> fail for you? My host is stretch.
>
A while ago it was 100%: Tried multiconfig:qemuarm-buster:isar-image-base
multiple times in a row, without passing. Then it worked with
kasproject/kas-isar:1.0 which was stretch-based. And now it's even passing with
kas-isar:latest. Weird.
Jan
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2019-08-23 12:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-22 14:18 Jan Kiszka
2019-08-22 14:47 ` Baurzhan Ismagulov
2019-08-22 15:00 ` Jan Kiszka
2019-08-22 15:27 ` Baurzhan Ismagulov
2019-08-23 12:26 ` Jan Kiszka [this message]
2019-08-27 4:33 ` Baurzhan Ismagulov
2019-08-27 7:10 ` Jan Kiszka
2019-09-03 15:44 ` Baurzhan Ismagulov
2019-09-03 16:23 ` Jan Kiszka
2019-09-03 17:02 ` Jan Kiszka
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=e4f22b4a-8f7b-183a-776a-4a9991a1db84@siemens.com \
--to=jan.kiszka@siemens.com \
--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