All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Anthony PERARD <anthony.perard@vates.tech>
Cc: Xen-devel <xen-devel@lists.xenproject.org>,
	"Juergen Gross" <jgross@suse.com>,
	"Roger Pau Monné" <roger.pau@citrix.com>,
	"Jan Beulich" <JBeulich@suse.com>,
	"Stefano Stabellini" <sstabellini@kernel.org>,
	"Julien Grall" <julien@xen.org>,
	"Oleksii Kurochko" <oleksii.kurochko@gmail.com>,
	"Shawn Anastasio" <sanastasio@raptorengineering.com>,
	"Olaf Hering" <olaf@aepfle.de>
Subject: Re: [PATCH v2 13/12] CI: Refresh OpenSUSE Tumbleweed container
Date: Fri, 12 Jul 2024 13:48:18 +0100	[thread overview]
Message-ID: <f3ebf546-64b2-4e35-a679-ae53865cfa78@citrix.com> (raw)
In-Reply-To: <ZpEiqM7XWlzb4q+z@l14>

On 12/07/2024 1:33 pm, Anthony PERARD wrote:
> On Fri, Jul 12, 2024 at 12:14:26PM +0100, Andrew Cooper wrote:
>> while removed are:
>>
>>   bc                   # ?
> I don't know why, but this one is also installed by osstest. The commit
> adding it doesn't say why it was needed.
>
> Also, looks like many QEMU containers are installing `bc`, but I can't
> find a single use. Maybe historic.

Part of the reason why our containers are so massive is because
dependencies only ever accumulate...

But yes - this one is especially odd.
>>   nasm                 # ?
> 'nasm' is used to build OVMF.
>
>
> If we don't want to build OVMF in our GitLab CI, which I don't think
> would be useful to do anyway (no dependency on xen.git)

Oh, interesting.

I'd assumed (by virtue of the jobs succeeding) that we were building
OVMF by default, but we're clearly not.

./configure says:

  --enable-ovmf           Enable OVMF (default is DISABLED)

so it's really just a simple opt-in, which our build script does not.


In the longer term, we will want OVMF in Gitlab CI, but we'd want to
pull it in as a separate artefact and use
--with-system-ovmf=/path/to/artefact

So I agree we don't need to build OVMF inside this container.

> , then:
>
> Reviewed-by: Anthony PERARD <anthony.perard@vates.tech>

Thanks.

~Andrew


  reply	other threads:[~2024-07-12 12:48 UTC|newest]

Thread overview: 72+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-11 11:15 [PATCH for-4.19 v2 00/12] CI: part 3 (slimline, and PPC/RISCV fixes) Andrew Cooper
2024-07-11 11:15 ` [PATCH 01/12] CI: Fix CONTAINER_UID0=1 scripts/containerize Andrew Cooper
2024-07-11 12:54   ` Anthony PERARD
2024-07-11 11:15 ` [PATCH 02/12] CI: Remove useless/misleading randconfig jobs Andrew Cooper
2024-07-11 13:09   ` Anthony PERARD
2024-07-11 15:16     ` Andrew Cooper
2024-07-11 15:50       ` Anthony PERARD
2024-07-11 16:03         ` Andrew Cooper
2024-07-11 11:15 ` [PATCH 03/12] CI: Drop Debian Jessie dockerfiles Andrew Cooper
2024-07-11 15:27   ` Anthony PERARD
2024-07-11 11:15 ` [PATCH 04/12] CI: Drop Debian Stretch testing Andrew Cooper
2024-07-11 13:20   ` Anthony PERARD
2024-07-11 11:15 ` [PATCH 05/12] CI: Drop Ubuntu Trusty testing Andrew Cooper
2024-07-11 13:26   ` Anthony PERARD
2024-07-11 11:15 ` [PATCH 06/12] CI: Mark Archlinux/x86 as allowing failures Andrew Cooper
2024-07-11 13:37   ` Anthony PERARD
2024-07-11 15:24     ` Andrew Cooper
2024-07-11 11:15 ` [PATCH 07/12] CI: Introduce a debian:12-ppc64le container Andrew Cooper
2024-07-11 14:41   ` Anthony PERARD
2024-07-11 15:50     ` Andrew Cooper
2024-07-11 11:15 ` [PATCH 08/12] CI: Use debian:12-ppc64le for both build and test Andrew Cooper
2024-07-11 16:22   ` Anthony PERARD
2024-07-11 18:08     ` Andrew Cooper
2024-07-11 11:15 ` [PATCH 09/12] CI: Refresh bullseye-ppc64le as debian:11-ppc64le Andrew Cooper
2024-07-11 16:27   ` Anthony PERARD
2024-07-11 11:15 ` [PATCH 10/12] CI: Introduce debian:11/12-riscv64 containers Andrew Cooper
2024-07-11 16:34   ` Anthony PERARD
2024-07-12 11:39   ` Oleksii
2024-07-12 12:30     ` Andrew Cooper
2024-07-15 13:29       ` Oleksii
2024-07-11 11:15 ` [PATCH 11/12] CI: Swap to debian for riscv64 build and test Andrew Cooper
2024-07-11 16:37   ` Anthony PERARD
2024-07-12 11:40   ` Oleksii
2024-07-11 11:15 ` [PATCH 12/12] CI: Refresh and upgrade the GCC-IBT container Andrew Cooper
2024-07-11 16:42   ` Anthony PERARD
2024-07-11 13:33 ` [PATCH for-4.19 v2 00/12] CI: part 3 (slimline, and PPC/RISCV fixes) Oleksii
2024-07-11 20:23 ` [PATCH 13/12] CI: Refresh OpenSUSE Tumbleweed container Andrew Cooper
2024-07-11 21:04   ` Andrew Cooper
2024-07-11 21:49   ` Olaf Hering
2024-07-11 22:39     ` Andrew Cooper
2024-07-12  6:37       ` Olaf Hering
2024-07-12 11:14   ` [PATCH v2 " Andrew Cooper
2024-07-12 12:33     ` Anthony PERARD
2024-07-12 12:48       ` Andrew Cooper [this message]
2024-07-11 21:05 ` [PATCH 14/12] CI: Refresh OpenSUSE Leap container Andrew Cooper
2024-07-12 12:55   ` [PATCH v2 " Andrew Cooper
2024-07-12 13:02     ` Anthony PERARD
2024-07-12 10:48 ` [PATCH 15/12] CI: Refresh Ubuntu Xenial container as 16.04-x86_64 Andrew Cooper
2024-07-12 13:57   ` Anthony PERARD
2024-07-12 14:02   ` Anthony PERARD
2024-07-12 14:05     ` Andrew Cooper
2024-07-12 14:29   ` Anthony PERARD
2024-07-12 15:43     ` Andrew Cooper
2024-07-12 10:48 ` [PATCH 16/12] CI: Refresh Ubuntu Bionic container as 18.04-x86_64 Andrew Cooper
2024-07-12 14:12   ` Anthony PERARD
2024-07-12 14:13     ` Andrew Cooper
2024-07-12 10:48 ` [PATCH 17/12] CI: Refresh Ubuntu Focal container as 20.04-x86_64 Andrew Cooper
2024-07-12 16:29   ` Anthony PERARD
2024-07-12 10:49 ` [PATCH 18/12] CI: Add Ubuntu 22.04 (Jammy) and 24.04 (Noble) testing Andrew Cooper
2024-07-12 16:44   ` Anthony PERARD
2024-07-12 17:01     ` Andrew Cooper
2024-07-13 18:09 ` [PATCH 19/12] docs: Fix install-man$(1)-pages if no manpages are generated Andrew Cooper
2024-07-15 12:05   ` Anthony PERARD
2024-07-13 18:09 ` [PATCH 20/12] CI: Swap from perl to perl-base in build containers Andrew Cooper
2024-07-15 12:46   ` Anthony PERARD
2024-07-15 13:02     ` Andrew Cooper
2024-07-13 18:10 ` [PATCH 21/12] CI: Refresh and upgrade the Fedora container Andrew Cooper
2024-07-15 13:39   ` Anthony PERARD
2024-07-15 14:39     ` Andrew Cooper
2024-07-15 15:16 ` [PATCH 22/12] tools/examples: Remove more obsolete content Andrew Cooper
2024-07-15 16:53   ` Anthony PERARD
2024-07-15 17:17     ` Andrew Cooper

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=f3ebf546-64b2-4e35-a679-ae53865cfa78@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=anthony.perard@vates.tech \
    --cc=jgross@suse.com \
    --cc=julien@xen.org \
    --cc=olaf@aepfle.de \
    --cc=oleksii.kurochko@gmail.com \
    --cc=roger.pau@citrix.com \
    --cc=sanastasio@raptorengineering.com \
    --cc=sstabellini@kernel.org \
    --cc=xen-devel@lists.xenproject.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.