From: Thomas Huth <thuth@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>, qemu-devel@nongnu.org
Cc: "Beraldo Leal" <bleal@redhat.com>,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
"Yonggang Luo" <luoyonggang@gmail.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Bin Meng" <bin.meng@windriver.com>
Subject: Re: [PATCH] gitlab: remove duplication between msys jobs
Date: Wed, 26 Jul 2023 20:21:33 +0200 [thread overview]
Message-ID: <0d0f9f65-2ead-6852-20c2-a83e256eecac@redhat.com> (raw)
In-Reply-To: <20230726161942.229093-1-berrange@redhat.com>
On 26/07/2023 18.19, Daniel P. Berrangé wrote:
> Although they share a common parent, the two msys jobs still have
> massive duplication in their script definitions that can easily be
> collapsed.
>
> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
> ---
> .gitlab-ci.d/windows.yml | 132 +++++++++++++++------------------------
> 1 file changed, 49 insertions(+), 83 deletions(-)
We originally had different sets of packages in the 32-bit and 64-bit jobs,
to distribute the load between the two jobs ... but it got unified in commit
14547e0877f3522. Now considering that we are facing timeouts again, we
should maybe rather revert that commit instead of unifying the lists forever?
Anyway, before we unify the compiler package name suffix between the two
jobs, I really would like to see whether the mingw Clang builds QEMU faster
in the 64-bit job ... but so far I failed to convince meson to accept the
Clang from the mingw package ... does anybody know how to use Clang with
MSYS2 properly?
Thomas
next prev parent reply other threads:[~2023-07-26 19:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-26 16:19 [PATCH] gitlab: remove duplication between msys jobs Daniel P. Berrangé
2023-07-26 18:21 ` Thomas Huth [this message]
2023-07-26 18:42 ` Marc-André Lureau
2023-07-27 10:39 ` Daniel P. Berrangé
2023-07-28 8:35 ` Thomas Huth
2023-07-28 8:58 ` Daniel P. Berrangé
2023-07-28 9:32 ` Marc-André Lureau
2023-07-28 9:50 ` Thomas Huth
2023-07-28 10:01 ` Thomas Huth
2023-07-28 10:39 ` Daniel P. Berrangé
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=0d0f9f65-2ead-6852-20c2-a83e256eecac@redhat.com \
--to=thuth@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=bin.meng@windriver.com \
--cc=bleal@redhat.com \
--cc=luoyonggang@gmail.com \
--cc=marcandre.lureau@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=wainersm@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).