From: Thomas Huth <thuth@redhat.com>
To: Qemu-block <qemu-block@nongnu.org>
Cc: Kevin Wolf <kwolf@redhat.com>, Fam Zheng <fam@euphon.net>,
QEMU Developers <qemu-devel@nongnu.org>,
Max Reitz <mreitz@redhat.com>
Subject: [Qemu-devel] qemu iotest 192 does not clean up correctly
Date: Wed, 8 May 2019 10:14:57 +0200 [thread overview]
Message-ID: <aac34cba-a184-f059-20f1-fb1e7e219d0b@redhat.com> (raw)
I've ran into this failure today:
140 0s ... - output mismatch (see 140.out.bad)
--- /home/thuth/devel/qemu/tests/qemu-iotests/140.out 2019-05-07 17:57:08.000000000 +0200
+++ /home/thuth/tmp/qemu-build/tests/qemu-iotests/140.out.bad 2019-05-08 07:19:23.000000000 +0200
@@ -10,6 +10,8 @@
{"return": {}}
qemu-io: can't open device nbd+unix:///drv?socket=TEST_DIR/nbd: Requested export not available
server reported: export 'drv' not present
+mkfifo: cannot create fifo '/home/thuth/tmp/qemu-build/tests/qemu-iotests/scratch/qmp-out-27628_0': File exists
+mkfifo: cannot create fifo '/home/thuth/tmp/qemu-build/tests/qemu-iotests/scratch/qmp-in-27628_0': File exists
{"return": {}}
{"timestamp": {"seconds": TIMESTAMP, "microseconds": TIMESTAMP}, "event": "SHUTDOWN", "data": {"guest": false, "reason": "host-qmp-quit"}}
*** done
... and indeed, there were lots of stale qmp-in-* and qmp-out-*
files in my scratch directory, ultimately causing the above failure
after a couple of days.
After some more testing, it seems like test 192 is not cleaning up
correctly:
$ ls scratch/
$ ./check -qcow2 192
[...]
192 0s ...
Passed all 1 tests
$ ls scratch/
nbd qemu-0.pid qmp-in-8772_0 qmp-out-8772_0
Any ideas how to fix this in a clean way (e.g. simply add a
"rm -f scratch/..." at the end of the script) ?
Thomas
next reply other threads:[~2019-05-08 8:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-08 8:14 Thomas Huth [this message]
2019-05-08 12:40 ` [Qemu-devel] qemu iotest 192 does not clean up correctly Max Reitz
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=aac34cba-a184-f059-20f1-fb1e7e219d0b@redhat.com \
--to=thuth@redhat.com \
--cc=fam@euphon.net \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--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).