From: "Cédric Le Goater" <clegoate@redhat.com>
To: Michael Tokarev <mjt@tls.msk.ru>,
QEMU Developers <qemu-devel@nongnu.org>
Cc: Vikram Garhwal <vikram.garhwal@amd.com>,
Francisco Iglesias <francisco.iglesias@amd.com>,
Richard Henderson <richard.henderson@linaro.org>
Subject: Re: intermittent qtest-aarch64/xlnx-canfd-test test failure
Date: Mon, 30 Oct 2023 17:19:38 +0100 [thread overview]
Message-ID: <76165393-f7ef-40fb-883f-ba8654856467@redhat.com> (raw)
In-Reply-To: <fd2b7868-2ac5-64a1-d66f-3025c1da6bd1@tls.msk.ru>
On 9/21/23 09:51, Michael Tokarev wrote:
> Hi!
>
> While doing stable-8.1.1 preparation, I've a CI failure of ubuntu-20.04-s390x-all here:
>
> https://gitlab.com/qemu-project/qemu/-/jobs/5132720046
>
> ▶ ERROR:../tests/qtest/xlnx-canfd-test.c:265:match_rx_tx_data: \
> assertion failed ((buf_rx[size] & DLC_FD_BIT_MASK) == (buf_tx[size] & DLC_FD_BIT_MASK)): (2281701376 == 2147483648)
>
> qemu:qtest+qtest-aarch64 / qtest-aarch64/xlnx-canfd-test \
> ERROR 0.77s killed by signal 6 SIGABRT
>
> Re-run of this test went successfully. However, the assert looks
> a bit scary, and the fact that it does not fail in a reliable way
> is a bit troubling too. Is it a flaky test or there's something
> else in qemu with concurrent threads?
>
> I don't see this assert in previous test runs. But ubuntu-20.04-s390x-all
> test fails quite often due to other reasons, so it isn't conclusive.
>
> Should something be done with this?
>
> The testing is done for commit f2fc49c302036315db6e8c9f74592decc3be0476,
> which is in staging-8.1 branch only temporarily.
>
> Thanks,
>
> /mjt
>
I had the same CI error in job https://gitlab.com/legoater/qemu/-/jobs/5416150239
▶ 170/258 ERROR:../tests/qtest/xlnx-canfd-test.c:265:match_rx_tx_data: assertion failed ((buf_rx[size] & DLC_FD_BIT_MASK) == (buf_tx[size] & DLC_FD_BIT_MASK)): (2281701376 == 2147483648) ERROR
170/258 qemu:qtest+qtest-aarch64 / qtest-aarch64/xlnx-canfd-test ERROR 0.49s killed by signal 6 SIGABRT
>>> QTEST_QEMU_BINARY=./qemu-system-aarch64 PYTHON=/builds/legoater/qemu/build/pyvenv/bin/python3 MALLOC_PERTURB_=60 G_TEST_DBUS_DAEMON=/builds/legoater/qemu/tests/dbus-vmstate-daemon.sh /builds/legoater/qemu/build/tests/qtest/xlnx-canfd-test --tap -k
――――――――――――――――――――――――――――――――――――― ✀ ―――――――――――――――――――――――――――――――――――――
stderr:
**
ERROR:../tests/qtest/xlnx-canfd-test.c:265:match_rx_tx_data: assertion failed ((buf_rx[size] & DLC_FD_BIT_MASK) == (buf_tx[size] & DLC_FD_BIT_MASK)): (2281701376 == 2147483648)
(test program exited with status code -6)
I could reproduce on PPC64 and s390x systems.
C.
next prev parent reply other threads:[~2023-10-30 16:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-21 7:51 intermittent qtest-aarch64/xlnx-canfd-test test failure Michael Tokarev
2023-10-30 16:19 ` Cédric Le Goater [this message]
2023-10-31 20:19 ` Vikram Garhwal
2023-11-06 14:47 ` Cédric Le Goater
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=76165393-f7ef-40fb-883f-ba8654856467@redhat.com \
--to=clegoate@redhat.com \
--cc=francisco.iglesias@amd.com \
--cc=mjt@tls.msk.ru \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=vikram.garhwal@amd.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).