From: Bin Meng <bmeng.cn@gmail.com>
To: Thomas Huth <thuth@redhat.com>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
qemu-devel@nongnu.org, "Alex Bennée" <alex.bennee@linaro.org>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Bin Meng" <bin.meng@windriver.com>,
"Stefan Weil" <sw@weilnetz.de>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>
Subject: Re: [PATCH] .gitlab-ci.d/windows: Work-around timeout and OpenGL problems of the MSYS2 jobs
Date: Fri, 6 Jan 2023 17:24:01 +0800 [thread overview]
Message-ID: <CAEUhbmUsvseOFDru-Hnw4co-+VNKHDPKne_-Dpj1jPD03w=VnQ@mail.gmail.com> (raw)
In-Reply-To: <b3fe53d9-67c5-9e22-d5e7-fa98cac5cd58@redhat.com>
On Fri, Jan 6, 2023 at 3:35 AM Thomas Huth <thuth@redhat.com> wrote:
>
> On 05/01/2023 09.34, Thomas Huth wrote:
> > On 04/01/2023 23.01, Peter Maydell wrote:
> >> On Wed, 4 Jan 2023 at 12:36, Thomas Huth <thuth@redhat.com> wrote:
> >>>
> >>> The windows jobs (especially the 32-bit job) recently started to
> >>> hit the timeout limit. Bump it a little bit to ease the situation
> >>> (80 minutes is quite long already - OTOH, these jobs do not have to
> >>> wait for a job from the container stage to finish, so this should
> >>> still be OK).
> >>>
> >>> Additionally, some update on the container side recently enabled
> >>> OpenGL in these jobs - but the corresponding code fails to compile.
> >>> Thus disable OpenGL here for the time being until someone figured
> >>> out the proper fix in the shader code for this.
> >>>
> >>> Signed-off-by: Thomas Huth <thuth@redhat.com>
> >>> ---
> >>> Now that the timeout and OpenGL problems are gone, the 64-bit is
> >>> working fine for me again. However, I'm still seeing random issues
> >>> with the 32-bit job ... not sure whether it's a problem on the
> >>> QEMU side or whether the builders are currently instable, since
> >>> the issues do not reproduce reliably...
> >>>
> >>> .gitlab-ci.d/windows.yml | 7 ++++---
> >>> 1 file changed, 4 insertions(+), 3 deletions(-)
> >>
> >> Thanks; applied to master on the assumption it will improve the
> >> CI situation. I found that the msys2-32bit job still timed out
> >> at 1h20, though:
> >>
> >> https://gitlab.com/qemu-project/qemu/-/jobs/3555245586
> >
> > I just gave it a try again, too, and for me, it finished within 65 minutes:
> >
> > https://gitlab.com/thuth/qemu/-/jobs/3557600268
> >
> > ... let's keep looking for a while, maybe it's ok in most cases now, but if
> > not, we have to consider something else.
>
> Ok, so after I've been struggling with a failing msys2-32bit job for my new
> upcoming pull request the last two days (I thought I had a bad patch in
> there), where I had some problems with the test-hmp and qom-test qtests,
> I've come up with a new theory after looking at this CI run from the
> qemu-project staging branch and seeing that these tests are also failing there:
>
> https://gitlab.com/qemu-project/qemu/-/jobs/3558798544
> https://gitlab.com/qemu-project/qemu/-/jobs/3560870904
>
> That might also explain the timed-out job that you have seen earlier, Peter,
> it was likely a hanging qom-test since that seems to be the first test to be
> executed during the "make check" there.
>
> So the qtests for Windows are definitely not ready for the CI yet (after
> we've enabled them just in December). I think it's best to disable them
> there again completely until the issues are understood and fixed.
>
I cannot reproduce the test failures of both tests (test-hmp and
qom-test) with w32 executables. Neither did the w64 executables.
My testing repo is at commit d1852caab131ea898134fdcea8c14bc2ee75fbe9.
Regards,
Bin
next prev parent reply other threads:[~2023-01-06 9:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-04 12:35 [PATCH] .gitlab-ci.d/windows: Work-around timeout and OpenGL problems of the MSYS2 jobs Thomas Huth
2023-01-04 12:46 ` Philippe Mathieu-Daudé
2023-01-04 14:54 ` Marc-André Lureau
2023-01-04 22:01 ` Peter Maydell
2023-01-05 8:34 ` Thomas Huth
2023-01-05 19:25 ` Thomas Huth
2023-01-06 9:24 ` Bin Meng [this message]
2023-01-07 14:32 ` Thomas Huth
2023-01-06 17:08 ` Volker Rümelin
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='CAEUhbmUsvseOFDru-Hnw4co-+VNKHDPKne_-Dpj1jPD03w=VnQ@mail.gmail.com' \
--to=bmeng.cn@gmail.com \
--cc=alex.bennee@linaro.org \
--cc=bin.meng@windriver.com \
--cc=marcandre.lureau@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=sw@weilnetz.de \
--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).