From: Baurzhan Ismagulov <ibr@radix50.net>
To: isar-users <isar-users@googlegroups.com>
Subject: Re: isar-bootstrap failures with debian-buster targets
Date: Thu, 22 Aug 2019 16:47:08 +0200 [thread overview]
Message-ID: <20190822144706.GA6062@yssyq.m.ilbers.de> (raw)
In-Reply-To: <cae4e0e1-0e57-e69d-fbce-7f9ea46d5818@siemens.com>
Hello Jan,
On Thu, Aug 22, 2019 at 04:18:57PM +0200, Jan Kiszka wrote:
> only on my machine so far, I'm seeing weird failures of buster-targeting
> non-x86 builds, primarily armhf and also mipsel. The pattern is always
> some out-of-memory inside apt during "apt-get update":
...
> Anyone any idea? Build host is latest kas-project/kas-isar, i.e. a
> Debian 10 instance.
Is it reproducible with stock Isar?
Is it reproducible outside of docker?
With kind regards,
Baurzhan.
next prev parent reply other threads:[~2019-08-22 14:47 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 [this message]
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
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=20190822144706.GA6062@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