From: Jan Kiszka <jan.kiszka@siemens.com>
To: isar-users <isar-users@googlegroups.com>
Subject: Re: isar-bootstrap failures with debian-buster targets
Date: Tue, 27 Aug 2019 09:10:21 +0200 [thread overview]
Message-ID: <5b671fed-4dbc-1beb-e9bd-3f67b1a804df@siemens.com> (raw)
In-Reply-To: <20190827043332.GJ6062@yssyq.m.ilbers.de>
On 27.08.19 06:33, Baurzhan Ismagulov wrote:
> On Fri, Aug 23, 2019 at 02:26:57PM +0200, Jan Kiszka wrote:
>> 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.
>
> FWIW, this also occurred on an internal Jenkins machine (stretch host, stretch
> workspace, no docker). This happening only with buster target, we have only two
> candidates: bug in qemu or bug Debian, no?
Yeah, stretch host does not seem to make a difference. I've seen it meanwhile
also with the stretch-based kas image.
Should we try to file bug? Question is: against which component? debootstrap?
Jan
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2019-08-27 7:10 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
2019-08-27 4:33 ` Baurzhan Ismagulov
2019-08-27 7:10 ` Jan Kiszka [this message]
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=5b671fed-4dbc-1beb-e9bd-3f67b1a804df@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