From: Peter Maydell <peter.maydell@linaro.org>
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: "Philippe Mathieu-Daudé" <philmd@linaro.org>,
qemu-devel@nongnu.org, "Thomas Huth" <thuth@redhat.com>,
"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:47:53 +0000 [thread overview]
Message-ID: <CAFEAcA_z=uXM-Ez-DZDpOd4OP-DPfmEjOX0bHR66igALhvm-NA@mail.gmail.com> (raw)
In-Reply-To: <87v86g8zbd.fsf@draig.linaro.org>
On Thu, 22 Feb 2024 at 12:21, Alex Bennée <alex.bennee@linaro.org> wrote:
>
> Peter Maydell <peter.maydell@linaro.org> writes:
> > Is there a reason why we aren't covering those in Windows
> > builds?
>
> I think it came down to the Windows builds being particularly prone to
> timing out and these targets being fairly niche. Do we really expect to
> catch build failures here that the other more featured targets wont?
In my experience, yes, the weirdo host platforms (big-endian,
32-bit, Windows, BSD) are the ones that developers won't be
testing on and that we therefore want to have CI for the full
range of target configs on. It's safer to skip niche targets
on non-niche hosts (read x86-64 Linux) because you can be
reasonably sure the niche-target developers test on that host.
thanks
-- PMM
next prev parent reply other threads:[~2024-02-22 12:48 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
2024-02-22 12:21 ` Alex Bennée
2024-02-22 12:47 ` Peter Maydell [this message]
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='CAFEAcA_z=uXM-Ez-DZDpOd4OP-DPfmEjOX0bHR66igALhvm-NA@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=luoyonggang@gmail.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.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).