From: Thomas Huth <thuth@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>,
John Snow <jsnow@redhat.com>, Alberto Garcia <berto@igalia.com>,
Vladimir Sementsov-Ogievskiy <vsementsov@yandex-team.ru>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
Qemu-block <qemu-block@nongnu.org>
Subject: Re: test-blockjob: intermittent CI failures in msys2-64bit job
Date: Fri, 17 Mar 2023 13:35:50 +0100 [thread overview]
Message-ID: <df71d7b5-7723-eaff-3dcd-45f69186f6af@redhat.com> (raw)
In-Reply-To: <CAFEAcA-n+9N+0ZuE6MSD1aMBeGYAJTbQe=j1-2K=SgD_Ly6nEA@mail.gmail.com>
On 17/03/2023 11.17, Peter Maydell wrote:
> On Mon, 6 Mar 2023 at 11:16, Peter Maydell <peter.maydell@linaro.org> wrote:
>>
>> On Fri, 3 Mar 2023 at 18:36, Peter Maydell <peter.maydell@linaro.org> wrote:
>>>
>>> I've noticed that test-blockjob seems to fail intermittently
>>> on the msys2-64bit job:
>>>
>>> https://gitlab.com/qemu-project/qemu/-/jobs/3872508803
>>> https://gitlab.com/qemu-project/qemu/-/jobs/3871061024
>>> https://gitlab.com/qemu-project/qemu/-/jobs/3865312440
>>>
>>> Sample output:
>>> | 53/89 ERROR:../tests/unit/test-blockjob.c:499:test_complete_in_standby:
>>> assertion failed: (job->status == JOB_STATUS_STANDBY) ERROR
>>> 53/89 qemu:unit / test-blockjob ERROR 0.08s exit status 3
>
>> Here's an intermittent failure from my macos x86 machine:
>>
>> 172/621 qemu:unit / test-blockjob
>> ERROR 0.26s killed by signal 6 SIGABRT
>
> And an intermittent on the freebsd 13 CI job:
> https://gitlab.com/qemu-project/qemu/-/jobs/3950667240
>
>>>> MALLOC_PERTURB_=197 G_TEST_BUILDDIR=/tmp/cirrus-ci-build/build/tests/unit G_TEST_SRCDIR=/tmp/cirrus-ci-build/tests/unit /tmp/cirrus-ci-build/build/tests/unit/test-blockjob --tap -k
> ▶ 178/650 /blockjob/ids
> OK
> 178/650 qemu:unit / test-blockjob
> ERROR 0.31s killed by signal 6 SIGABRT
> ――――――――――――――――――――――――――――――――――――― ✀ ―――――――――――――――――――――――――――――――――――――
> stderr:
> Assertion failed: (job->status == JOB_STATUS_STANDBY), function
> test_complete_in_standby, file ../tests/unit/test-blockjob.c, line
> 499.
>
>
> TAP parsing error: Too few tests run (expected 9, got 1)
> (test program exited with status code -6)
> ――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――
>
> Anybody in the block team looking at these, or shall we just
> disable this test entirely ?
I ran into this issue today, too:
https://gitlab.com/thuth/qemu/-/jobs/3954367101
... if nobody is interested in fixing this test, I think we should disable it...
Thomas
next prev parent reply other threads:[~2023-03-17 12:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-03 18:36 test-blockjob: intermittent CI failures in msys2-64bit job Peter Maydell
2023-03-06 11:16 ` Peter Maydell
2023-03-17 10:17 ` Peter Maydell
2023-03-17 12:35 ` Thomas Huth [this message]
2023-04-21 10:13 ` Vladimir Sementsov-Ogievskiy
2023-04-24 13:36 ` Emanuele Giuseppe Esposito
2023-04-24 18:32 ` Vladimir Sementsov-Ogievskiy
2023-04-25 16:48 ` Hanna Czenczek
2023-04-25 16:58 ` Vladimir Sementsov-Ogievskiy
2023-04-26 7:38 ` Emanuele Giuseppe Esposito
2023-04-26 8:03 ` Hanna Czenczek
2023-04-26 8:17 ` Emanuele Giuseppe Esposito
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=df71d7b5-7723-eaff-3dcd-45f69186f6af@redhat.com \
--to=thuth@redhat.com \
--cc=berto@igalia.com \
--cc=jsnow@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=vsementsov@yandex-team.ru \
/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).