From: Jan Kiszka <jan.kiszka@siemens.com>
To: "Maxim Yu. Osipov" <mosipov@ilbers.de>
Cc: Henning Schild <henning.schild@siemens.com>,
isar-users <isar-users@googlegroups.com>,
Cedric Hombourger <Cedric_Hombourger@mentor.com>
Subject: Re: [PATCH] isar-bootstrap: Fix and cleanup bind mounting
Date: Fri, 30 Nov 2018 10:38:11 +0100 [thread overview]
Message-ID: <8fd7b05e-0f90-12b3-30f5-e17b173e5927@siemens.com> (raw)
In-Reply-To: <cd0d2bc1-92e5-116e-ad8a-2075fc7cc441@ilbers.de>
On 30.11.18 10:20, Maxim Yu. Osipov wrote:
> Hi Jan,
>
> I've just tried this patch (on the 'next' with reverted patch d40a9ac0) and ran
> "fast" CI
>
> isar$mount | wc -l
> 34
>
> isar$./scripts/ci_build.sh -q -f
>
> CI script hung on CI stage when dpkg-base is modified
> causing rebuilding recipes based on dpkg-base.
>
> The mount reports less (!) mount points than before launching the script.
>
> mount | wc -l
> 31
I will try to reproduce locally. So far, none of the test I made with downstream
layers reported issues. But we may have more hidden bugs...
Jan
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2018-11-30 9:38 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-29 16:29 Jan Kiszka
2018-11-29 18:39 ` Henning Schild
2018-11-30 9:20 ` Maxim Yu. Osipov
2018-11-30 9:36 ` Henning Schild
2018-11-30 9:40 ` Jan Kiszka
2018-11-30 9:38 ` Jan Kiszka [this message]
2018-11-30 10:19 ` Jan Kiszka
2018-11-30 10:51 ` Jan Kiszka
2018-12-03 12:59 ` Jan Kiszka
2018-12-03 14:37 ` Hombourger, Cedric
2018-12-04 10:49 ` Maxim Yu. Osipov
2018-12-04 14:24 ` Jan Kiszka
2018-12-04 15:42 ` Jan Kiszka
2018-12-04 15:45 ` Hombourger, Cedric
2018-12-04 16:59 ` Maxim Yu. Osipov
2018-12-04 17:10 ` Jan Kiszka
2018-12-04 17:31 ` Jan Kiszka
2018-12-04 15:45 ` Jan Kiszka
2018-12-07 13:45 ` Maxim Yu. Osipov
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=8fd7b05e-0f90-12b3-30f5-e17b173e5927@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=Cedric_Hombourger@mentor.com \
--cc=henning.schild@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