From: Thomas Huth <thuth@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@gmail.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: egl compile error on msys CI runners
Date: Wed, 29 Mar 2023 10:20:36 +0200 [thread overview]
Message-ID: <93c25ac1-7af7-1d3f-1d91-498f341a57d5@redhat.com> (raw)
In-Reply-To: <ZCPxrZT+JlBNL/b6@redhat.com>
On 29/03/2023 10.07, Daniel P. Berrangé wrote:
> On Wed, Mar 29, 2023 at 11:01:35AM +0400, Marc-André Lureau wrote:
>> Hi Peter
>>
>> On Tue, Mar 28, 2023 at 6:39 PM Peter Maydell <peter.maydell@linaro.org> wrote:
>>>
>>> The msys CI runners have started failing to compile with an EGL
>>> related error:
>>>
>>> https://gitlab.com/qemu-project/qemu/-/jobs/4015682307
>>>
>>> In file included from
>>> C:/GitLab-Runner/builds/qemu-project/qemu/msys64/mingw64/include/epoxy/egl.h:46,
>>> from C:/GitLab-Runner/builds/qemu-project/qemu/include/ui/egl-helpers.h:5,
>>> from ../ui/egl-helpers.c:21:
>>> C:/GitLab-Runner/builds/qemu-project/qemu/msys64/mingw64/include/epoxy/egl_generated.h:11:10:
>>> fatal error: EGL/eglplatform.h: No such file or directory
>>> 11 | #include "EGL/eglplatform.h"
>>> | ^~~~~~~~~~~~~~~~~~~
>>> ninja: build stopped: subcommand failed.
>>>
>>> Dan says this is because of a msys2 packaging issue:
>>> https://github.com/msys2/MINGW-packages/issues/16492
>>>
>>> Can we have a meson test that doesn't try to enable EGL on systems
>>> like this one where it's broken ? Changing the current meson.build
>>> if cc.has_header('epoxy/egl.h', dependencies: epoxy)
>>> to whatever the meson is for "actually try to compile with the
>>> header" ought to do the trick, I think.
>>>
>>
>> This is an unfortunate consequence of using a fast-moving rolling
>> distribution, there are random breakages. It would make sense to have
>> tagged / pre-built images instead. That would also speed up the CI a
>> bit, hopefully.
>
> IMHO if the distro is considered susceptible to ongoing random
> breakage we must not use it as a gating CI job. IOW, these
> msys jobs should have 'allow-failure: true' added to their
> definition.
I'm not a fan of 'allow-failure: true' - that basically means nobody will
look at the failing jobs, so we could rather disable the jobs by default
instead (and just run them manually when you want to have a look at them).
Thomas
next prev parent reply other threads:[~2023-03-29 8:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-28 14:38 egl compile error on msys CI runners Peter Maydell
2023-03-29 7:01 ` Marc-André Lureau
2023-03-29 7:23 ` Thomas Huth
2023-03-29 8:07 ` Daniel P. Berrangé
2023-03-29 8:20 ` Thomas Huth [this message]
2023-03-29 10:22 ` 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=93c25ac1-7af7-1d3f-1d91-498f341a57d5@redhat.com \
--to=thuth@redhat.com \
--cc=berrange@redhat.com \
--cc=marcandre.lureau@gmail.com \
--cc=peter.maydell@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).