public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Henning Schild <henning.schild@siemens.com>
To: "Moessbauer, Felix" <felix.moessbauer@siemens.com>
Cc: Anton Mikanovich <amikan@ilbers.de>,
	isar-users <isar-users@googlegroups.com>,
	"jan.kiszka@siemens.com" <jan.kiszka@siemens.com>
Subject: Re: [PATCH] ci-build: Protect bullseye container with KFAIL
Date: Thu, 29 Apr 2021 19:43:03 +0200	[thread overview]
Message-ID: <20210429194303.3cd264fb@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <AM0PR10MB193985F2FACA67F98EB06E20895F9@AM0PR10MB1939.EURPRD10.PROD.OUTLOOK.COM>

Am Thu, 29 Apr 2021 14:05:34 +0000
schrieb "Moessbauer, Felix" <felix.moessbauer@siemens.com>:

> Hi,
> 
> I stumbled upon that while debugging the build errors on the DKMS
> module patch. If possible, we could just bump QEMU in the KAS image
> to have a proper fix.

Additions to the kas images need to go to the kas ML. the CI of
ilbers/isar does not use kas so we might need to detect and skip if
possible

ilbers not using kas is a problem that i think is being worked on, but
it also has value to make sure isar does not depend on kas

Henning

> Otherwise, we might run into that issue here and there and it's not
> obvious that this is the root cause. I don't think that the patch
> will be integrated into buster, so we can't just wait for it. 
> 
> Anyways, at least a warning message should be emitted when running on
> the broken version.
> 
> PS: sending this to the list as well.
> 
> Best regards,
> Felix
> 
> > -----Original Message-----
> > From: Anton Mikanovich <amikan@ilbers.de>
> > Sent: Thursday, April 29, 2021 4:01 PM
> > To: Moessbauer, Felix (T RDA IOT SES-DE)
> > <felix.moessbauer@siemens.com> Cc: Kiszka, Jan (T RDA IOT)
> > <jan.kiszka@siemens.com> Subject: Re: [PATCH] ci-build: Protect
> > bullseye container with KFAIL
> > 
> > 29.04.2021 16:42, Moessbauer, Felix wrote:  
> > > Hi Anton,
> > >
> > > I can confirm that the CI patch does not solve the issue (on
> > > mc:qemuarm64-  
> > focal).  
> > > In case of the gitlab-ci, the KAS image provides the
> > > qemu-user-static.
> > >
> > > I just tried to install qemu-user-static from buster-backports
> > > into the KAS  
> > container and that solved the issue.  
> > > Maybe Jan might have a look into that. IMO this would be way
> > > better than  
> > trying to work-around in ISAR.  
> > >
> > > Best regards,
> > > Felix  
> > 
> > Sure that was just an ugly hotfix to not have all CI builds 'red'
> > because of that.
> > When the original issue will be solved we can remove those KFAILs.
> > 
> > --
> > 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  
> 


  reply	other threads:[~2021-04-29 17:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-09  8:15 Anton Mikanovich
     [not found] ` <AM0PR10MB1939FA7325472104729E5ADC895F9@AM0PR10MB1939.EURPRD10.PROD.OUTLOOK.COM>
     [not found]   ` <982a11de-e990-5334-3896-2b96f7364715@ilbers.de>
2021-04-29 14:05     ` Moessbauer, Felix
2021-04-29 17:43       ` Henning Schild [this message]
     [not found]   ` <a4a7c550-ee88-2b3b-3f5b-20b0f32a1dfe@siemens.com>
2021-04-30  7:49     ` Moessbauer, Felix
2021-04-30 17:57       ` Jan Kiszka
2021-04-30 18:31         ` 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=20210429194303.3cd264fb@md1za8fc.ad001.siemens.net \
    --to=henning.schild@siemens.com \
    --cc=amikan@ilbers.de \
    --cc=felix.moessbauer@siemens.com \
    --cc=isar-users@googlegroups.com \
    --cc=jan.kiszka@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