From: Richard Henderson <richard.henderson@linaro.org>
To: "Marc-André Lureau" <marcandre.lureau@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: vhost-user-test failure
Date: Thu, 7 Jul 2022 06:48:33 +0530 [thread overview]
Message-ID: <fc85a25a-2679-b3c0-ad21-04a2a590dc5a@linaro.org> (raw)
Seen on my ubuntu 22.04 laptop:
86/591 qemu:qtest+qtest-i386 / qtest-i386/qos-test ERROR
10.74s killed by signal 6 SIGABRT
# child process (/i386/pc/i440FX-pcihost/pci-bus-pc/pci-bus/virtio-net-pci/virti
o-net/virtio-net-tests/vhost-user/reconnect/subprocess [1677921]) stderr: "qemu-
system-i386: -chardev socket,id=chr-reconnect,path=/tmp/vhost-test-MdgDF8/reconn
ect.sock,server=on: info: QEMU waiting for connection on: disconnected:unix:/tmp
/vhost-test-MdgDF8/reconnect.sock,server=on\nqemu-system-i386: Failed to set msg
fds.\nqemu-system-i386: vhost VQ 0 ring restore failed: -22: Invalid argument (
22)\nqemu-system-i386: Failed to set msg fds.\nqemu-system-i386: vhost VQ 1 ring
restore failed: -22: Invalid argument (22)\n**\nERROR:../src/tests/qtest/vhost-
user-test.c:809:wait_for_rings_started: assertion failed (ctpop64(s->rings) == c
ount): (1 == 2)\n"
Bail out! ERROR:../src/tests/qtest/qos-test.c:189:subprocess_run_one_test: child
process (/i386/pc/i440FX-pcihost/pci-bus-pc/pci-bus/virtio-net-pci/virtio-net/v
irtio-net-tests/vhost-user/reconnect/subprocess [1677921]) failed unexpectedly
stderr:
**
ERROR:../src/tests/qtest/qos-test.c:189:subprocess_run_one_test: child process
(/i386/pc/i440FX-pcihost/pci-bus-pc/pci-bus/virtio-net-pci/virtio-net/virtio-net-tests/vhost-user/reconnect/subprocess
[1677921]) failed unexpectedly
The failure appears to be timeout related, so it's not consistent, but some of the error
messages embedded in that block suggest the test never really got started correctly?
r~
reply other threads:[~2022-07-07 1:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=fc85a25a-2679-b3c0-ad21-04a2a590dc5a@linaro.org \
--to=richard.henderson@linaro.org \
--cc=marcandre.lureau@redhat.com \
--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).