From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Xen-devel <xen-devel@lists.xenproject.org>
Cc: "Anthony PERARD" <anthony.perard@vates.tech>,
"Michal Orzel" <michal.orzel@amd.com>,
"Jan Beulich" <jbeulich@suse.com>,
"Julien Grall" <julien@xen.org>,
"Roger Pau Monné" <roger.pau@citrix.com>,
"Stefano Stabellini" <sstabellini@kernel.org>,
"Oleksii Kurochko" <oleksii.kurochko@gmail.com>
Subject: Re: [PATCH 1/3] CI: Update build tests based on new minimum toolchain requirements
Date: Thu, 20 Mar 2025 16:01:36 +0000 [thread overview]
Message-ID: <ef8fbae6-e231-4348-843b-bf84eaf0ef52@citrix.com> (raw)
In-Reply-To: <20250320155908.43885-2-andrew.cooper3@citrix.com>
Test, to try and figure out what inumbo is choking on.
~Andrew
On 20/03/2025 3:59 pm, Andrew Cooper wrote:
> Drop CentOS 7 entirely. It's way to old now.
>
> Ubuntu 22.04 is the oldest Ubuntu with a suitable version of Clang, so swap
> the 16.04 clang builds for 22.04.
>
> Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
> ---
> CC: Anthony PERARD <anthony.perard@vates.tech>
> CC: Michal Orzel <michal.orzel@amd.com>
> CC: Jan Beulich <jbeulich@suse.com>
> CC: Julien Grall <julien@xen.org>
> CC: Roger Pau Monné <roger.pau@citrix.com>
> CC: Stefano Stabellini <sstabellini@kernel.org>
> CC: Oleksii Kurochko <oleksii.kurochko@gmail.com>
> ---
> automation/build/centos/7.dockerfile | 72 ----------------------------
> automation/gitlab-ci/build.yaml | 30 ++++--------
> 2 files changed, 10 insertions(+), 92 deletions(-)
> delete mode 100644 automation/build/centos/7.dockerfile
>
> diff --git a/automation/build/centos/7.dockerfile b/automation/build/centos/7.dockerfile
> deleted file mode 100644
> index f41dda732084..000000000000
> --- a/automation/build/centos/7.dockerfile
> +++ /dev/null
> @@ -1,72 +0,0 @@
> -# syntax=docker/dockerfile:1
> -FROM --platform=linux/amd64 centos:7
> -LABEL maintainer.name="The Xen Project" \
> - maintainer.email="xen-devel@lists.xenproject.org"
> -
> -RUN mkdir /build
> -WORKDIR /build
> -
> -RUN <<EOF
> - set -e
> -
> - # Fix up Yum config now that mirror.centos.org doesn't exist
> - sed -e 's/mirror.centos.org/vault.centos.org/g' \
> - -e 's/^#.*baseurl=https\?/baseurl=https/g' \
> - -e 's/^mirrorlist=https\?/#mirrorlist=https/g' \
> - -i /etc/yum.repos.d/*.repo
> -
> - # Add the EPEL repo to get dev86
> - yum -y install epel-release
> -
> - # Update everything (Base container is out of date)
> - yum -y update
> -
> - DEPS=(
> - # Xen
> - binutils
> - gcc
> - make
> - python
> - # Kconfig
> - bison
> - flex
> - # Flask
> - checkpolicy
> -
> - # Tools (general)
> - git
> - gzip
> - patch
> - perl
> - pkgconfig
> - wget
> - # libxenguest dombuilder
> - bzip2-devel
> - lz4-devel
> - lzo-devel
> - xz-devel
> - zlib-devel
> - zstd-devel
> - # libacpi
> - acpica-tools
> - # libxl
> - libuuid-devel
> - yajl-devel
> - # RomBIOS
> - dev86
> - # Header Check
> - gcc-c++
> - # xentop
> - ncurses-devel
> - # Python bindings
> - python-devel
> -
> - # Stubdom download/extract
> - bzip2
> - )
> -
> - yum -y install "${DEPS[@]}"
> -
> - yum clean all
> - rm -rf /var/cache/yum
> -EOF
> diff --git a/automation/gitlab-ci/build.yaml b/automation/gitlab-ci/build.yaml
> index f633068c312b..2513908b059b 100644
> --- a/automation/gitlab-ci/build.yaml
> +++ b/automation/gitlab-ci/build.yaml
> @@ -545,16 +545,6 @@ archlinux-gcc-debug:
> CONTAINER: archlinux:current
> allow_failure: true
>
> -centos-7-gcc:
> - extends: .gcc-x86-64-build
> - variables:
> - CONTAINER: centos:7
> -
> -centos-7-gcc-debug:
> - extends: .gcc-x86-64-build-debug
> - variables:
> - CONTAINER: centos:7
> -
> debian-12-x86_64-gcc-ibt:
> extends: .gcc-x86-64-build
> variables:
> @@ -607,16 +597,6 @@ fedora-41-x86_64-gcc-debug:
> variables:
> CONTAINER: fedora:41-x86_64
>
> -ubuntu-16.04-x86_64-clang:
> - extends: .clang-x86-64-build
> - variables:
> - CONTAINER: ubuntu:16.04-x86_64
> -
> -ubuntu-16.04-x86_64-clang-debug:
> - extends: .clang-x86-64-build-debug
> - variables:
> - CONTAINER: ubuntu:16.04-x86_64
> -
> ubuntu-16.04-x86_64-gcc:
> extends: .gcc-x86-64-build
> variables:
> @@ -637,6 +617,16 @@ ubuntu-20.04-x86_64-gcc:
> variables:
> CONTAINER: ubuntu:20.04-x86_64
>
> +ubuntu-22.04-x86_64-clang:
> + extends: .clang-x86-64-build
> + variables:
> + CONTAINER: ubuntu:22.04-x86_64
> +
> +ubuntu-22.04-x86_64-clang-debug:
> + extends: .clang-x86-64-build-debug
> + variables:
> + CONTAINER: ubuntu:22.04-x86_64
> +
> ubuntu-22.04-x86_64-gcc:
> extends: .gcc-x86-64-build
> variables:
next prev parent reply other threads:[~2025-03-20 16:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-20 15:59 [PATCH RESEND 0/3] Xen: CI changes for new toolchain baseline Andrew Cooper
2025-03-20 15:59 ` [PATCH 2/3] Xen: Update compiler checks Andrew Cooper
2025-03-21 22:10 ` Stefano Stabellini
2025-03-20 15:59 ` [PATCH 3/3] CHANGELOG: Minimum toolchain requirements Andrew Cooper
2025-03-21 16:24 ` Oleksii Kurochko
2025-03-27 15:45 ` Andrew Cooper
2025-03-27 16:55 ` Oleksii Kurochko
2025-03-27 17:03 ` Andrew Cooper
[not found] ` <20250320155908.43885-2-andrew.cooper3@citrix.com>
2025-03-20 16:01 ` Andrew Cooper [this message]
2025-03-25 15:46 ` [PATCH 1/3] CI: Update build tests based on new minimum " Anthony PERARD
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=ef8fbae6-e231-4348-843b-bf84eaf0ef52@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=anthony.perard@vates.tech \
--cc=jbeulich@suse.com \
--cc=julien@xen.org \
--cc=michal.orzel@amd.com \
--cc=oleksii.kurochko@gmail.com \
--cc=roger.pau@citrix.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.