From: Anthony PERARD <anthony@xenproject.org>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: Xen-devel <xen-devel@lists.xenproject.org>,
"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>,
"Shawn Anastasio" <sanastasio@raptorengineering.com>,
"Oleksii Kurochko" <oleksii.kurochko@gmail.com>,
"Doug Goldstein" <cardoe@cardoe.com>,
"Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>,
"Victor Lira" <victorm.lira@amd.com>
Subject: Re: [PATCH 2/5] CI: Update ppc64 to use Debian Trixie
Date: Wed, 13 Aug 2025 17:16:58 +0200 [thread overview]
Message-ID: <aJysartA4Sh6bdTE@l14> (raw)
In-Reply-To: <20250809221206.1260861-3-andrew.cooper3@citrix.com>
On Sat, Aug 09, 2025 at 11:12:03PM +0100, Andrew Cooper wrote:
> diff --git a/automation/gitlab-ci/build.yaml b/automation/gitlab-ci/build.yaml
> index ab5211f77e5e..3fe539dc5683 100644
> --- a/automation/gitlab-ci/build.yaml
> +++ b/automation/gitlab-ci/build.yaml
> @@ -319,10 +319,10 @@ debian-12-x86_64-clang-debug:
> variables:
> CONTAINER: debian:12-x86_64
>
> -debian-12-ppc64le-gcc-debug:
> +debian-13-ppc64le-gcc-debug:
> extends: .gcc-ppc64le-cross-build-debug
> variables:
> - CONTAINER: debian:12-ppc64le
> + CONTAINER: debian:13-ppc64le
> KBUILD_DEFCONFIG: ppc64_defconfig
> HYPERVISOR_ONLY: y
> EXTRA_XEN_CONFIG: |
> @@ -705,6 +705,20 @@ debian-12-ppc64le-gcc:
> KBUILD_DEFCONFIG: ppc64_defconfig
> HYPERVISOR_ONLY: y
>
> +debian-12-ppc64le-gcc-debug:
> + extends: .gcc-ppc64le-cross-build-debug
> + variables:
> + CONTAINER: debian:12-ppc64le
> + KBUILD_DEFCONFIG: ppc64_defconfig
> + HYPERVISOR_ONLY: y
> +
Why did you remove the EXTRA_XEN_CONFIG from this job? Currently, the
job is setup as:
debian-12-ppc64le-gcc-debug:
extends: .gcc-ppc64le-cross-build-debug
variables:
CONTAINER: debian:12-ppc64le
KBUILD_DEFCONFIG: ppc64_defconfig
HYPERVISOR_ONLY: y
EXTRA_XEN_CONFIG: |
CONFIG_UBSAN=y
CONFIG_UBSAN_FATAL=y
Thanks,
--
Anthony PERARD
next prev parent reply other threads:[~2025-08-13 15:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-09 22:12 [PATCH for-4.21 0/5] CI: Add Debian Trixie Andrew Cooper
2025-08-09 22:12 ` [PATCH 1/5] CI: Trixie containers Andrew Cooper
[not found] ` <37edbe9d-3c14-422b-b21b-49a5fa25a453@gmail.com>
2025-08-11 9:56 ` Andrew Cooper
2025-08-09 22:12 ` [PATCH 2/5] CI: Update ppc64 to use Debian Trixie Andrew Cooper
2025-08-13 15:16 ` Anthony PERARD [this message]
2025-09-10 15:56 ` Andrew Cooper
2025-08-09 22:12 ` [PATCH 3/5] CI: Update riscv64 " Andrew Cooper
2025-08-11 8:43 ` Oleksii Kurochko
2025-08-11 9:56 ` Andrew Cooper
2025-08-11 15:23 ` Oleksii Kurochko
2025-08-09 22:12 ` [PATCH 4/5] stubdom: Fix -Wimplicit-int in newlib Andrew Cooper
2025-08-10 6:14 ` Jürgen Groß
2025-08-09 22:12 ` [PATCH 5/5] CI: Update x86 to use Debian Trixie Andrew Cooper
2025-08-11 8:32 ` [PATCH for-4.21 0/5] CI: Add " Oleksii Kurochko
2025-09-09 11:48 ` Marek Marczykowski-Górecki
2025-09-09 21:53 ` Stefano Stabellini
2025-09-11 7:48 ` Oleksii Kurochko
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=aJysartA4Sh6bdTE@l14 \
--to=anthony@xenproject.org \
--cc=andrew.cooper3@citrix.com \
--cc=anthony.perard@vates.tech \
--cc=cardoe@cardoe.com \
--cc=jbeulich@suse.com \
--cc=julien@xen.org \
--cc=marmarek@invisiblethingslab.com \
--cc=michal.orzel@amd.com \
--cc=oleksii.kurochko@gmail.com \
--cc=roger.pau@citrix.com \
--cc=sanastasio@raptorengineering.com \
--cc=sstabellini@kernel.org \
--cc=victorm.lira@amd.com \
--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.