From: "Daniel P. Berrangé" <berrange@redhat.com>
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: qemu-devel@nongnu.org, "Ed Maste" <emaste@freebsd.org>,
"Akihiko Odaki" <odaki@rsg.ci.i.u-tokyo.ac.jp>,
"Thomas Huth" <thuth@redhat.com>,
"BALATON Zoltan" <balaton@eik.bme.hu>,
"Sriram Yagnaraman" <sriram.yagnaraman@ericsson.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"David Woodhouse" <dwmw2@infradead.org>,
"Paul Durrant" <paul@xen.org>,
"Gustavo Romero" <gustavo.romero@linaro.org>,
"Kohei Tokunaga" <ktokunaga.mail@gmail.com>,
"Li-Wen Hsu" <lwhsu@freebsd.org>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Dmitry Osipenko" <dmitry.osipenko@collabora.com>,
qemu-arm@nongnu.org, "Zhao Liu" <zhao1.liu@intel.com>,
qemu-s390x@nongnu.org
Subject: Re: [PATCH v3 16/18] gitlab: make custom runners need QEMU_CI to run
Date: Mon, 17 Nov 2025 11:59:59 +0000 [thread overview]
Message-ID: <aRsOP1FY8akZ376B@redhat.com> (raw)
In-Reply-To: <20251117115523.3993105-17-alex.bennee@linaro.org>
On Mon, Nov 17, 2025 at 11:55:21AM +0000, Alex Bennée wrote:
> In addition to not being triggered by schedule we should follow the
> same rules about QEMU_CI. One day we may figure out how to fold the
> custom runner rules into the .base_job_template but today is not that
> day.
>
> Message-ID: <20251113102525.1255370-17-alex.bennee@linaro.org>
> Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
>
> ---
> v3
> - re-jigged to ensure staging still runs
> ---
> .gitlab-ci.d/custom-runners/debian-13-ppc64le.yml | 4 ++++
> .gitlab-ci.d/custom-runners/ubuntu-24.04-aarch64.yml | 4 ++++
> .gitlab-ci.d/custom-runners/ubuntu-24.04-s390x.yml | 4 ++++
> 3 files changed, 12 insertions(+)
Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
With regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2025-11-17 12:00 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-17 11:55 [PATCH v3 00/18] testing/next cleanups (docker, functional) - pre-PR-final-1 Alex Bennée
2025-11-17 11:55 ` [PATCH v3 01/18] tests/docker: drop --link from COPYs in emsdk docker Alex Bennée
2025-11-17 11:55 ` [PATCH v3 02/18] libvirt-ci: bump libvirt-ci to latest version Alex Bennée
2025-11-17 11:55 ` [PATCH v3 03/18] tests/lcitool: update ENV stazas outputted by refresh Alex Bennée
2025-11-17 14:00 ` Philippe Mathieu-Daudé
2025-11-17 15:50 ` Alex Bennée
2025-11-17 11:55 ` [PATCH v3 04/18] tests/docker: add coreutils to the package list Alex Bennée
2025-11-17 11:55 ` [PATCH v3 05/18] docs/about/emulation: update assets for uftrace plugin documentation Alex Bennée
2025-11-17 11:55 ` [PATCH v3 06/18] tests: move test_xen assets to share.linaro.org Alex Bennée
2025-11-17 11:55 ` [PATCH v3 07/18] tests: move test_virt " Alex Bennée
2025-11-17 11:55 ` [PATCH v3 08/18] tests: move test_netdev_ethtool " Alex Bennée
2025-11-17 11:55 ` [PATCH v3 09/18] tests: move test_kvm_xen " Alex Bennée
2025-11-17 11:55 ` [PATCH v3 10/18] tests: move test_kvm " Alex Bennée
2025-11-17 11:55 ` [PATCH v3 11/18] tests: move test_virt_gpu " Alex Bennée
2025-11-17 11:55 ` [PATCH v3 12/18] gitlab: add initial ppc64le custom-runner test Alex Bennée
2025-11-17 11:55 ` [PATCH v3 13/18] gitlab: use template for ubuntu-24.04-s390x jobs Alex Bennée
2025-11-17 11:55 ` [PATCH v3 14/18] gitlab: simplify the ubuntu-24.04-aarch64 rules Alex Bennée
2025-11-17 11:55 ` [PATCH v3 15/18] gitlab: suppress custom runners being triggered by schedule Alex Bennée
2025-11-17 11:55 ` [PATCH v3 16/18] gitlab: make custom runners need QEMU_CI to run Alex Bennée
2025-11-17 11:59 ` Daniel P. Berrangé [this message]
2025-11-17 11:55 ` [PATCH v3 17/18] gitlab: make the schedule rules a bit more general Alex Bennée
2025-11-17 11:55 ` [PATCH v3 18/18] gitlab: add a weekly container building job Alex Bennée
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=aRsOP1FY8akZ376B@redhat.com \
--to=berrange@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=balaton@eik.bme.hu \
--cc=dmitry.osipenko@collabora.com \
--cc=dwmw2@infradead.org \
--cc=emaste@freebsd.org \
--cc=gustavo.romero@linaro.org \
--cc=ktokunaga.mail@gmail.com \
--cc=lwhsu@freebsd.org \
--cc=odaki@rsg.ci.i.u-tokyo.ac.jp \
--cc=paul@xen.org \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=sriram.yagnaraman@ericsson.com \
--cc=thuth@redhat.com \
--cc=zhao1.liu@intel.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;
as well as URLs for NNTP newsgroup(s).