From: Thomas Huth <thuth@redhat.com>
To: "Peter Maydell" <peter.maydell@linaro.org>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>
Cc: qemu-devel@nongnu.org, "Daniel P. Berrangé" <berrange@redhat.com>,
"Yonggang Luo" <luoyonggang@gmail.com>
Subject: Re: [PATCH 2/3] .gitlab-ci.d: Drop cross-win32-system job
Date: Thu, 22 Feb 2024 12:56:38 +0100 [thread overview]
Message-ID: <83ba064a-d0ec-46c0-a6a3-f767350c5542@redhat.com> (raw)
In-Reply-To: <CAFEAcA_1zEQ-bT8bE=74FC24fz7HYN6j8ZLZVaDn7C47vraNAQ@mail.gmail.com>
On 22/02/2024 12.44, Peter Maydell wrote:
> On Tue, 20 Feb 2024 at 18:46, Philippe Mathieu-Daudé <philmd@linaro.org> wrote:
>>
>> On 20/2/24 18:44, Peter Maydell wrote:
>>> We don't support 32-bit Windows any more, so we don't need to defend it
>>> with this CI job.
>>>
>>> Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
>>> ---
>>> .gitlab-ci.d/container-cross.yml | 5 -
>>> .gitlab-ci.d/crossbuilds.yml | 14 ---
>>> .../dockerfiles/fedora-win32-cross.docker | 111 ------------------
>>> tests/lcitool/refresh | 5 -
>>> 4 files changed, 135 deletions(-)
>>> delete mode 100644 tests/docker/dockerfiles/fedora-win32-cross.docker
>>
>>
>>> diff --git a/.gitlab-ci.d/crossbuilds.yml b/.gitlab-ci.d/crossbuilds.yml
>>> index d19d98cde05..987ba9694ba 100644
>>> --- a/.gitlab-ci.d/crossbuilds.yml
>>> +++ b/.gitlab-ci.d/crossbuilds.yml
>>> @@ -159,20 +159,6 @@ cross-mips64el-kvm-only:
>>> IMAGE: debian-mips64el-cross
>>> EXTRA_CONFIGURE_OPTS: --disable-tcg --target-list=mips64el-softmmu
>>>
>>> -cross-win32-system:
>>> - extends: .cross_system_build_job
>>> - needs:
>>> - job: win32-fedora-cross-container
>>> - variables:
>>> - IMAGE: fedora-win32-cross
>>> - EXTRA_CONFIGURE_OPTS: --enable-fdt=internal
>>> - CROSS_SKIP_TARGETS: alpha-softmmu avr-softmmu hppa-softmmu m68k-softmmu
>>> - microblazeel-softmmu mips64el-softmmu nios2-softmmu
>>
>> Thomas, is it possible to add mips64el-softmmu to the cross-win64-system
>> job or is it already at the timeout limit?
>
> This is a skip, i.e. exclude, list, not an include list. So dropping
> this job is not removing mips64el-softmmu from coverage.
> The Windows build coverage we lose will be the targets we
> are skipping in the cross-win64-system job and weren't
> skipping here:
> or1k-softmmu rx-softmmu sh4eb-softmmu sparc64-softmmu
> tricore-softmmu xtensaeb-softmmu
>
> which then fall into the same bucket as
> alpha-softmmu avr-softmmu hppa-softmmu m68k-softmmu
> microblazeel-softmmu nios2-softmmu
>
> which are already not built in either cross-win*-system job.
>
> Is there a reason why we aren't covering those in Windows
> builds?
I guess it's just an arbitrary list to keep the compilation time within the
timeout limits.
Thomas
next prev parent reply other threads:[~2024-02-22 11:57 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-20 17:44 [PATCH 0/3] Drop 32-bit Windows as a supported platform Peter Maydell
2024-02-20 17:44 ` [PATCH 1/3] docs: Document that 32-bit Windows is unsupported Peter Maydell
2024-02-20 18:02 ` Alex Bennée
2024-02-20 18:02 ` Daniel P. Berrangé
2024-02-21 7:10 ` Thomas Huth
2024-02-20 17:44 ` [PATCH 2/3] .gitlab-ci.d: Drop cross-win32-system job Peter Maydell
2024-02-20 18:02 ` Alex Bennée
2024-02-20 18:04 ` Daniel P. Berrangé
2024-02-20 18:46 ` Philippe Mathieu-Daudé
2024-02-20 18:55 ` Daniel P. Berrangé
2024-02-21 7:06 ` Thomas Huth
2024-02-22 11:44 ` Peter Maydell
2024-02-22 11:56 ` Thomas Huth [this message]
2024-02-22 12:21 ` Alex Bennée
2024-02-22 12:47 ` Peter Maydell
2024-02-21 7:11 ` Thomas Huth
2024-02-20 17:44 ` [PATCH 3/3] .gitlab-ci.d/windows.yml: Remove shared-msys2 abstraction Peter Maydell
2024-02-20 18:06 ` Daniel P. Berrangé
2024-02-21 7:16 ` Thomas Huth
2024-02-22 11:33 ` Peter Maydell
2024-02-20 18:50 ` Philippe Mathieu-Daudé
2024-02-22 11:38 ` Peter Maydell
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=83ba064a-d0ec-46c0-a6a3-f767350c5542@redhat.com \
--to=thuth@redhat.com \
--cc=berrange@redhat.com \
--cc=luoyonggang@gmail.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@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).