From: "Alex Bennée" <alex.bennee@linaro.org>
To: qemu-devel@nongnu.org
Subject: Re: [PULL 00/18] testing updates for 10.2
Date: Mon, 17 Nov 2025 16:49:29 +0000 [thread overview]
Message-ID: <87ms4kli3q.fsf@draig.linaro.org> (raw)
In-Reply-To: <20251117154948.4122164-1-alex.bennee@linaro.org> ("Alex Bennée"'s message of "Mon, 17 Nov 2025 15:49:29 +0000")
Alex Bennée <alex.bennee@linaro.org> writes:
> The following changes since commit e88510fcdc13380bd4895a17d6f8a0b3a3325b85:
>
> Merge tag 'pull-target-arm-20251114' of https://gitlab.com/pm215/qemu into staging (2025-11-14 17:59:05 +0100)
>
> are available in the Git repository at:
>
> https://gitlab.com/stsquad/qemu.git tags/pull-10.2-maintainer-171125-1
>
> for you to fetch changes up to 11a4716211766af6058ad517d73da97f37475e39:
>
> gitlab: add a weekly container building job (2025-11-17 15:43:35 +0000)
>
> ----------------------------------------------------------------
> testing updates for 10.2
>
> - fix emsdk image for podman
> - update lcitool and clean-up ENV stanzas
> - include coreutils for io tests
> - move a number of assets due to linaro changes
> - add ppc64le custom runner
> - rationalise the gitlab custom runners with templates
> - clean-up the custom runner rules
> - add a scheduled container build
Note I have sent a v2 very shortly after this one to address a single
typo....
Message-ID: <20251117155237.4124861-1-alex.bennee@linaro.org>
Date: Mon, 17 Nov 2025 15:52:37 +0000
Subject: [PULL v2 00/18] testing updates for 10.2
From: =?UTF-8?q?Alex=20Benn=C3=A9e?= <alex.bennee@linaro.org>
--
Alex Bennée
Virtualisation Tech Lead @ Linaro
prev parent reply other threads:[~2025-11-17 16:50 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-17 15:49 [PULL 00/18] testing updates for 10.2 Alex Bennée
2025-11-17 15:49 ` [PULL 01/18] tests/docker: drop --link from COPYs in emsdk docker Alex Bennée
2025-11-17 15:49 ` [PULL 02/18] libvirt-ci: bump libvirt-ci to latest version Alex Bennée
2025-11-17 15:49 ` [PULL 03/18] tests/lcitool: update ENV stazas outputted by refresh Alex Bennée
2025-11-17 15:49 ` [PULL 04/18] tests/docker: add coreutils to the package list Alex Bennée
2025-11-17 15:49 ` [PULL 05/18] docs/about/emulation: update assets for uftrace plugin documentation Alex Bennée
2025-11-17 15:49 ` [PULL 06/18] tests: move test_xen assets to share.linaro.org Alex Bennée
2025-11-17 15:49 ` [PULL 07/18] tests: move test_virt " Alex Bennée
2025-11-17 15:49 ` [PULL 08/18] tests: move test_netdev_ethtool " Alex Bennée
2025-11-17 15:49 ` [PULL 09/18] tests: move test_kvm_xen " Alex Bennée
2025-11-17 15:49 ` [PULL 10/18] tests: move test_kvm " Alex Bennée
2025-11-17 15:49 ` [PULL 11/18] tests: move test_virt_gpu " Alex Bennée
2025-11-17 15:49 ` [PULL 12/18] gitlab: add initial ppc64le custom-runner test Alex Bennée
2025-11-17 15:49 ` [PULL 13/18] gitlab: use template for ubuntu-24.04-s390x jobs Alex Bennée
2025-11-17 15:49 ` [PULL 14/18] gitlab: simplify the ubuntu-24.04-aarch64 rules Alex Bennée
2025-11-17 15:49 ` [PULL 15/18] gitlab: suppress custom runners being triggered by schedule Alex Bennée
2025-11-17 15:49 ` [PULL 16/18] gitlab: make custom runners need QEMU_CI to run Alex Bennée
2025-11-17 15:49 ` [PULL 17/18] gitlab: make the schedule rules a bit more general Alex Bennée
2025-11-17 15:49 ` [PULL 18/18] gitlab: add a weekly container building job Alex Bennée
2025-11-17 16:49 ` Alex Bennée [this message]
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=87ms4kli3q.fsf@draig.linaro.org \
--to=alex.bennee@linaro.org \
--cc=qemu-devel@nongnu.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 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).