From: Anton Mikanovich <amikan@ilbers.de>
To: Jan Kiszka <jan.kiszka@siemens.com>,
Gylstorff Quirin <quirin.gylstorff@siemens.com>,
isar-users@googlegroups.com
Subject: Re: [PATCH v14 0/2] CPIO & OVA Images
Date: Tue, 7 Sep 2021 16:49:00 +0300 [thread overview]
Message-ID: <278d86ea-9a93-07d8-ae2b-4030460a8d3c@ilbers.de> (raw)
In-Reply-To: <7bc7c5b0-01e3-f55e-2ced-d1dab24f327e@siemens.com>
07.09.2021 16:06, Jan Kiszka wrote:
> On 07.09.21 12:48, Gylstorff Quirin wrote:
>> I will test it on our site. with the patchset applied to next(
>> e274130b870b7e31532fe191b9932cde1d819b4b).
>>
> Full CI with your patches applied passed our nightly run today.
>
> Jan
>
As I've already mentioned, the issue is floating.
We have at least 4 failed builds in our CI, but even more without any
issues (with v14 in both groups). And none builds with the same issue
without v14 applied.
The last time it was seen at 2021-08-12, but I'm not able to reproduce
the issue after rebase on next.
Anyway now we need to rebase again to remove image_undo_mounts that was
gone after the last revert.
--
Anton Mikanovich
Promwad Ltd.
External service provider of ilbers GmbH
Maria-Merian-Str. 8
85521 Ottobrunn, Germany
+49 (89) 122 67 24-0
Commercial register Munich, HRB 214197
General Manager: Baurzhan Ismagulov
next prev parent reply other threads:[~2021-09-07 13:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-08 8:42 Q. Gylstorff
2021-07-08 8:42 ` [PATCH v14 1/2] meta/classes: Generate ova image for VMWare or Virtualbox Q. Gylstorff
2021-07-08 8:42 ` [PATCH v14 2/2] meta/classes: add cpiogz-img Q. Gylstorff
2021-08-20 9:07 ` [PATCH v14 0/2] CPIO & OVA Images Anton Mikanovich
2021-09-07 10:48 ` Gylstorff Quirin
2021-09-07 13:06 ` Jan Kiszka
2021-09-07 13:49 ` Anton Mikanovich [this message]
2021-09-13 9:39 ` Anton Mikanovich
2021-09-14 10:54 ` Henning Schild
2021-09-16 10:01 ` Henning Schild
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=278d86ea-9a93-07d8-ae2b-4030460a8d3c@ilbers.de \
--to=amikan@ilbers.de \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.com \
--cc=quirin.gylstorff@siemens.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