* [Qemu-devel] qemu iotest 192 does not clean up correctly
@ 2019-05-08 8:14 Thomas Huth
2019-05-08 12:40 ` Max Reitz
0 siblings, 1 reply; 2+ messages in thread
From: Thomas Huth @ 2019-05-08 8:14 UTC (permalink / raw)
To: Qemu-block; +Cc: Kevin Wolf, Fam Zheng, QEMU Developers, Max Reitz
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
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [Qemu-devel] qemu iotest 192 does not clean up correctly
2019-05-08 8:14 [Qemu-devel] qemu iotest 192 does not clean up correctly Thomas Huth
@ 2019-05-08 12:40 ` Max Reitz
0 siblings, 0 replies; 2+ messages in thread
From: Max Reitz @ 2019-05-08 12:40 UTC (permalink / raw)
To: Thomas Huth, Qemu-block; +Cc: Kevin Wolf, Fam Zheng, QEMU Developers
[-- Attachment #1: Type: text/plain, Size: 1510 bytes --]
On 08.05.19 10:14, Thomas Huth wrote:
>
> 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) ?
I think it’s just lacking a _cleanup_qemu.
Max
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2019-05-08 12:41 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2019-05-08 8:14 [Qemu-devel] qemu iotest 192 does not clean up correctly Thomas Huth
2019-05-08 12:40 ` Max Reitz
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).