public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Henning Schild <henning.schild@siemens.com>
To: Anton Mikanovich <amikan@ilbers.de>
Cc: <isar-users@googlegroups.com>
Subject: Re: [PATCH v3 0/5] Rebuild mount logic
Date: Tue, 8 Jun 2021 10:42:55 +0200	[thread overview]
Message-ID: <20210608104255.06246d5c@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <ae96adda-59a7-2f56-aa5a-a396eab48006@ilbers.de>

[-- Attachment #1: Type: text/plain, Size: 1062 bytes --]

Am Tue, 8 Jun 2021 11:15:26 +0300
schrieb Anton Mikanovich <amikan@ilbers.de>:

> 08.06.2021 10:58, Henning Schild wrote:
> > This series makes things not build in containers anymore, which we
> > heavily rely on for CI. Exceptions in the mount logic.
> >
> > I would suggest to revert and investigate.
> >
> > Henning  
> 
> There is no any build issues with container targets at
> ci.isar-build.org. Do you have any logs?

Not container targets, rather isar running inside a container. Our CI
does not run native because if severe security issues that would result
in. (need for sudo) And VMs are hard to set up.

Find the logs attached as a zip file.

I see the first error around 

ERROR: mc:qemuarm64-focal:hello-1.0-r0 do_apt_unpack:

This is a plain run of .gitlab-ci.yml, so using the container
"ghcr.io/siemens/kas/kas-isar:latest"

I guess can be reproduced with
cd isar
mkdir build
docker run --rm -t -i -v $(pwd):/this/:rw --privileged ghcr.io/siemens/kas/kas-isar:latest
sudo chown builder:builder build
scripts/ci_build.sh -q -f


regards,
Henning

[-- Attachment #2: logs-47819947.zip --]
[-- Type: application/zip, Size: 1367189 bytes --]

  reply	other threads:[~2021-06-08  8:47 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-08  6:25 Anton Mikanovich
2021-05-08  6:25 ` [PATCH v3 1/5] dpkg: Make mount buildroot reliable Anton Mikanovich
2021-06-08  8:09   ` Henning Schild
2021-06-08  8:31     ` Anton Mikanovich
2021-06-08  8:49       ` Henning Schild
2021-07-01 11:55   ` Jan Kiszka
2021-05-08  6:25 ` [PATCH v3 2/5] buildchroot: Unmount buildchroot mounts if not needed Anton Mikanovich
2021-05-08  6:25 ` [PATCH v3 3/5] rootfs: Unmount rootfs " Anton Mikanovich
2021-05-08  6:25 ` [PATCH v3 4/5] wic: Unmount dirs after usage Anton Mikanovich
2021-05-08  6:25 ` [PATCH v3 5/5] events: Warn if mounted paths left Anton Mikanovich
2021-07-01 11:51   ` Jan Kiszka
2021-06-08  7:58 ` [PATCH v3 0/5] Rebuild mount logic Henning Schild
2021-06-08  8:15   ` Anton Mikanovich
2021-06-08  8:42     ` Henning Schild [this message]
2021-06-08  8:54     ` Henning Schild
2021-06-10  7:12       ` Anton Mikanovich
2021-06-10 15:02         ` Henning Schild
2021-06-21 15:54 ` Jan Kiszka
2021-06-22 14:40   ` Anton Mikanovich

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=20210608104255.06246d5c@md1za8fc.ad001.siemens.net \
    --to=henning.schild@siemens.com \
    --cc=amikan@ilbers.de \
    --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