From: Greg Kurz <groug@kaod.org>
To: Cole Robinson <crobinso@redhat.com>
Cc: qemu_oss@crudebyte.com, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: virtio-9p-test.c:300:v9fs_req_recv: assertion failed (hdr.id == id): (7 == 73)
Date: Mon, 23 Nov 2020 14:17:34 +0100 [thread overview]
Message-ID: <20201123141734.0c03f21a@bahia.lan> (raw)
In-Reply-To: <fad8a69d-9c21-ac25-028d-646a64ccecc5@redhat.com>
Fixed maintainer's address: s/oss@crudebyte.com/qemu_oss@crudebyte.com
On Sat, 21 Nov 2020 17:03:14 -0500
Cole Robinson <crobinso@redhat.com> wrote:
> Hi, I'm consistently seeing this assertion running the qemu-5.2.0 test
> suite. rc0, rc1, rc2 have been consistently affected, it reproduces
> consistently in parts of Fedora's build system. Here's an example build
> log for rc2 x86 against Fedora 32
>
> https://download.copr.fedorainfracloud.org/results/@kubevirt/qemu-5.2.0-0.6.rc2/fedora-32-x86_64/01781514-qemu/builder-live.log.gz
>
> The full test error:
>
> ...
> PASS 26 qtest-arm/qos-test
> /arm/virt/virtio-mmio/virtio-bus/virtio-9p-device/virtio-9p/virtio-9p-tests/synth/readdir/split_128
> PASS 27 qtest-arm/qos-test
> /arm/virt/virtio-mmio/virtio-bus/virtio-9p-device/virtio-9p/virtio-9p-tests/local/config
Ok so the next test is supposed to be:
/arm/virt/virtio-mmio/virtio-bus/virtio-9p-device/virtio-9p/virtio-9p-tests/local/create_dir
This was added recently. This configures the virtio-9p device in QEMU
to serve a real test directory from the host. This test directory is
created under the current directory of the test process. The purpose
of the test is then to ask the 9p server to create a directory within
the test directory.
> Received response 7 (RLERROR) instead of 73 (RMKDIR)
> ERROR qtest-arm/qos-test - Bail out!
> ERROR:../tests/qtest/virtio-9p-test.c:300:v9fs_req_recv: assertion
> failed (hdr.id == id): (7 == 73)
> Rlerror has errno 95 (Operation not supported)
So this basically means that QEMU got ENOTSUP/EOPNOTSUPP when calling
mkdir() into the test directory... not sure what could cause that. I'd
need more details on the filesystem setup for the build.
Anyway, we already experienced some breakage in upstream CI because of
the same family of tests that do real access to the host filesystem.
Since they're being introduced in QEMU 5.2, I'll try to see if I can
disable them to be run by default for RC3.
Cheers,
--
Greg
> **
> ERROR:../tests/qtest/virtio-9p-test.c:300:v9fs_req_recv: assertion
> failed (hdr.id == id): (7 == 73)
> make: *** [Makefile.mtest:1257: run-test-155] Error 1
> error: Bad exit status from /var/tmp/rpm-tmp.EG4Dav (%check)
>
>
> Thanks,
> Cole
>
next prev parent reply other threads:[~2020-11-23 13:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-21 22:03 virtio-9p-test.c:300:v9fs_req_recv: assertion failed (hdr.id == id): (7 == 73) Cole Robinson
2020-11-23 13:17 ` Greg Kurz [this message]
2020-11-23 13:48 ` Christian Schoenebeck
2020-11-23 14:28 ` Greg Kurz
2020-11-23 19:45 ` Christian Schoenebeck
2020-11-24 13:25 ` Cole Robinson
2020-11-24 13:37 ` Christian Schoenebeck
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=20201123141734.0c03f21a@bahia.lan \
--to=groug@kaod.org \
--cc=crobinso@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu_oss@crudebyte.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).