From: "Alex Bennée" <alex.bennee@linaro.org>
To: Richard Henderson <richard.henderson@linaro.org>
Cc: qemu-devel@nongnu.org
Subject: Re: [PATCH 02/11] gitlab: drop aarch32 runner and associated bits
Date: Sun, 19 Oct 2025 23:12:58 +0100 [thread overview]
Message-ID: <87h5vu7d79.fsf@draig.linaro.org> (raw)
In-Reply-To: <cc5e4aba-7d88-4748-9368-cb8845c82150@linaro.org> (Richard Henderson's message of "Fri, 17 Oct 2025 10:56:19 -0700")
Richard Henderson <richard.henderson@linaro.org> writes:
> On 10/16/25 08:03, Alex Bennée wrote:
>> diff --git a/scripts/ci/setup/ubuntu/ubuntu-2204-armhf-cross.yml b/scripts/ci/setup/ubuntu/ubuntu-2204-armhf-cross.yml
>> deleted file mode 100644
>> index 0cc34cd10b9..00000000000
>> --- a/scripts/ci/setup/ubuntu/ubuntu-2204-armhf-cross.yml
>> +++ /dev/null
>> @@ -1,127 +0,0 @@
>> -# THIS FILE WAS AUTO-GENERATED
>> -#
>> -# $ lcitool variables --cross-arch armv7l ubuntu-2204 qemu
>> -#
>> -# https://gitlab.com/libvirt/libvirt-ci
>
>
> Had this file been missing from tests/lcitool/refresh?
It appears to have been added by hand. In an earlier patch series I had
to make some changes to lcitool to be able to generate yaml:
https://gitlab.com/stsquad/libvirt-ci/-/commits/cross-yaml-support
>
> There appear to be no more references to ubuntu2204, which is still
> present in the refresh script.
lcitool dockerfile --layers all ubuntu-2204 qemu
points to:
tests/tcg/docker/dockerfiles/ubuntu2204.docker
we will bump those in due course although probably not worth rushing
for 10.2.
>
>
> r~
--
Alex Bennée
Virtualisation Tech Lead @ Linaro
next prev parent reply other threads:[~2025-10-19 22:14 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-16 15:03 [PATCH 00/11] maintainer updates for October (gitlab, gpu, plugins, docs) pre-PR Alex Bennée
2025-10-16 15:03 ` [PATCH 01/11] gitlab: use template for ubuntu-24.04-aarch64 jobs Alex Bennée
2025-10-16 15:32 ` Pierrick Bouvier
2025-10-17 17:43 ` Richard Henderson
2025-10-16 15:03 ` [PATCH 02/11] gitlab: drop aarch32 runner and associated bits Alex Bennée
2025-10-16 15:31 ` Pierrick Bouvier
2025-10-17 17:56 ` Richard Henderson
2025-10-19 22:12 ` Alex Bennée [this message]
2025-10-16 15:03 ` [PATCH 03/11] tests/tcg/multiarch/linux/linux-test: Don't try to test atime update Alex Bennée
2025-10-17 18:02 ` Richard Henderson
2025-10-16 15:03 ` [PATCH 04/11] Support per-head resolutions with virtio-gpu Alex Bennée
2025-10-16 15:03 ` [PATCH 05/11] ui/gtk-gl-area: Remove extra draw call in refresh Alex Bennée
2025-10-16 15:03 ` [PATCH 06/11] hw/display: add blob map/unmap trace events Alex Bennée
2025-10-16 15:31 ` Pierrick Bouvier
2025-10-16 15:03 ` [PATCH 07/11] contrib/plugins/uftrace_symbols.py: generate debug files to map symbols to source Alex Bennée
2025-10-19 7:56 ` Akihiko Odaki
2025-10-19 17:24 ` Pierrick Bouvier
2025-10-16 15:03 ` [PATCH 08/11] docs/system: split VirtIO devices from the rest Alex Bennée
2025-10-16 15:03 ` [PATCH 09/11] docs/system: unify the naming style for VirtIO devices Alex Bennée
2025-10-16 15:03 ` [PATCH 10/11] docs/system: drop vhost-user-rng docs Alex Bennée
2025-10-16 15:03 ` [PATCH 11/11] docs/system: merge vhost-user-input into vhost-user-contrib 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=87h5vu7d79.fsf@draig.linaro.org \
--to=alex.bennee@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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).