From: Jan Kiszka <jan.kiszka@siemens.com>
To: "Maxim Yu. Osipov" <mosipov@ilbers.de>,
Andreas Reichel <andreas.reichel.ext@siemens.com>
Cc: isar-users@googlegroups.com
Subject: Re: [PATCH v7 0/5] Fix usage of additional apt keys and repos
Date: Wed, 20 Mar 2019 13:39:13 +0100 [thread overview]
Message-ID: <2c34ad6b-f600-b7dd-3127-371b4abdea44@siemens.com> (raw)
In-Reply-To: <451a9156-48f5-861a-6bde-6d059f49aa4b@ilbers.de>
On 20.03.19 12:05, Maxim Yu. Osipov wrote:
> On 3/20/19 11:37 AM, Jan Kiszka wrote:
>> On 20.03.19 11:25, Andreas Reichel wrote:
>>> On Wed, Mar 20, 2019 at 08:55:05AM +0100, Maxim Yu. Osipov wrote:
>>>> Hi Andreas, Jan,
>>>>
>>>> | I: Retrieving InRelease
>>>> | I: Checking Release signature
>>>> | E: Release signed by unknown key (key id 9165938D90FDDD2E)
>>>> | WARNING: exit code 1 from a shell command.
>>>> | ERROR: Function failed: do_bootstrap (log file is located at
>>>> /workspace/build/isar_mosipov_next/165/build/tmp/work/raspbian-jessie-armhf/isar-bootstrap-target/temp/log.do_bootstrap.12981)
>>>>
>>>> NOTE: recipe isar-bootstrap-target-1.0-r0: task do_bootstrap: Failed
>>>>
>>>> So, Andreas, please have a look on that.
>>>>
>>> @Jan, seems the build on siemens CI is NOT identical to the build on
>>> ilbers CI.
>>>
>>
>> We run the same script with the same parameters. But: We have different servers
>> (#number of cores) which can affect concurrency issues. And we have different
>> Internet connectivity, which can affect downloads (and also trigger concurrency
>> issues).
>
> We have debian-stretch-amd64 on isar-build.org.
>
> Which host system do you use in Siemens CI?
The kasproject/kas-isar container, the default for Isar builds by now. The host
is a Debian 9 as well, but that plays no significant role (except for kernel
issues).
The server is currently on 16-core machine. We will try to scale up in a couple
of weeks, adding a 32-core box to the cluster. And there will be a 128-core ARM
server available, but that likely only late summer.
Jan
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2019-03-20 12:39 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-19 13:35 Andreas J. Reichel
2019-03-19 13:35 ` [PATCH v7 1/5] Revert "isar-bootstrap: Allow to set local keys in DISTRO_APT_KEYS" Andreas J. Reichel
2019-03-19 13:35 ` [PATCH v7 2/5] Remove duplicate code from apt-keyring generation Andreas J. Reichel
2019-03-19 13:35 ` [PATCH v7 3/5] Fix fetched key location in apt-keyring generator Andreas J. Reichel
2019-03-19 13:35 ` [PATCH v7 4/5] Use apt-key to generate apt-keyring Andreas J. Reichel
2019-03-19 13:35 ` [PATCH v7 5/5] If we use a custom keyring debootstrap may fall to https Andreas J. Reichel
2019-03-19 13:36 ` [PATCH v7 0/5] Fix usage of additional apt keys and repos Andreas Reichel
2019-03-19 14:26 ` Maxim Yu. Osipov
2019-03-19 15:39 ` Andreas Reichel
2019-03-19 21:58 ` Maxim Yu. Osipov
2019-03-20 6:26 ` Jan Kiszka
2019-03-20 6:48 ` Maxim Yu. Osipov
2019-03-20 7:12 ` Jan Kiszka
2019-03-20 7:55 ` Maxim Yu. Osipov
2019-03-20 8:22 ` Jan Kiszka
2019-03-20 8:53 ` Maxim Yu. Osipov
2019-03-20 10:25 ` Andreas Reichel
2019-03-20 10:32 ` Maxim Yu. Osipov
2019-03-20 11:50 ` Andreas Reichel
2019-03-20 10:37 ` Jan Kiszka
2019-03-20 11:05 ` Maxim Yu. Osipov
2019-03-20 12:39 ` Jan Kiszka [this message]
2019-03-20 7:16 ` Claudius Heine
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=2c34ad6b-f600-b7dd-3127-371b4abdea44@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=andreas.reichel.ext@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=mosipov@ilbers.de \
/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