From: Anthony PERARD <anthony.perard@vates.tech>
To: Andrew Cooper <andrew.cooper3@citrix.com>
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>
Subject: Re: [PATCH 18/12] CI: Add Ubuntu 22.04 (Jammy) and 24.04 (Noble) testing
Date: Fri, 12 Jul 2024 16:44:55 +0000 [thread overview]
Message-ID: <ZpFdhgyybAAOEsE8@l14> (raw)
In-Reply-To: <20240712104907.3238026-1-andrew.cooper3@citrix.com>
On Fri, Jul 12, 2024 at 11:49:07AM +0100, Andrew Cooper wrote:
> The containers are exactly as per 20.04 (Focal). However, this now brings us
> to 5 releases * 4 build jobs worth of Ubuntu testing, which is overkill.
>
> The oldest and newest toolchains are the most likely to find problems with new
> code, so reduce the middle 3 releases (18/20/22) to just a single smoke test
> each.
That would mean a bit less `clang` build-test, but I guess that would be
mostly covered by FreeBSD testing on GitHub.
I tried to find out which version of clang were been used with this
patch applied:
Alpine clang version 16.0.6
Debian clang version 14.0.6
clang version 17.0.6
clang version 18.1.8
clang version 3.8.0-2ubuntu4 (tags/RELEASE_380/final)
Ubuntu clang version 18.1.3 (1ubuntu1)
and the versions that won't be tested anymore:
clang version 6.0.0-1ubuntu2 (tags/RELEASE_600/final)
clang version 10.0.0-4ubuntu1
Ubuntu clang version 14.0.0-1ubuntu1.1
> Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
Anyway:
Reviewed-by: Anthony PERARD <anthony.perard@vates.tech>
Thanks,
--
Anthony Perard | Vates XCP-ng Developer
XCP-ng & Xen Orchestra - Vates solutions
web: https://vates.tech
next prev parent reply other threads:[~2024-07-12 16:45 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
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 [this message]
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=ZpFdhgyybAAOEsE8@l14 \
--to=anthony.perard@vates.tech \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=jgross@suse.com \
--cc=julien@xen.org \
--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.