[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Qemu-block] iotest 141 fails with qed

From: Thomas Huth
Subject: [Qemu-block] iotest 141 fails with qed
Date: Wed, 17 Jul 2019 14:35:33 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.7.2

FWIW, I've got a new iotest failure with current master branch:

$ ./check -qed 141
QEMU          -- 
-nodefaults -machine accel=qtest
QEMU_IMG      -- "/tmp/qemu/tests/qemu-iotests/../../qemu-img" 
QEMU_IO       -- "/tmp/qemu/tests/qemu-iotests/../../qemu-io"  --cache 
writeback -f qed
QEMU_NBD      -- "/tmp/qemu/tests/qemu-iotests/../../qemu-nbd" 
IMGFMT        -- qed
IMGPROTO      -- file
PLATFORM      -- Linux/x86_64 thuth 3.10.0-957.21.3.el7.x86_64
TEST_DIR      -- /tmp/qemu/tests/qemu-iotests/scratch
SOCKET_SCM_HELPER -- /tmp/qemu/tests/qemu-iotests/socket_scm_helper

141      fail       [14:31:35] [14:31:36]                    output mismatch 
(see 141.out.bad)
--- /home/thuth/devel/qemu/tests/qemu-iotests/141.out   2019-07-15 
17:37:59.000000000 +0200
+++ /tmp/qemu/tests/qemu-iotests/141.out.bad    2019-07-17 14:31:36.142127948 
@@ -42,9 +42,9 @@
 {"return": {}}
 {"timestamp": {"seconds":  TIMESTAMP, "microseconds":  TIMESTAMP}, "event": 
"JOB_STATUS_CHANGE", "data": {"status": "created", "id": "job0"}}
 {"timestamp": {"seconds":  TIMESTAMP, "microseconds":  TIMESTAMP}, "event": 
"JOB_STATUS_CHANGE", "data": {"status": "running", "id": "job0"}}
-{"return": {}}
 {"timestamp": {"seconds":  TIMESTAMP, "microseconds":  TIMESTAMP}, "event": 
"JOB_STATUS_CHANGE", "data": {"status": "ready", "id": "job0"}}
 {"timestamp": {"seconds":  TIMESTAMP, "microseconds":  TIMESTAMP}, "event": 
"BLOCK_JOB_READY", "data": {"device": "job0", "len": 0, "offset": 0, "speed": 
0, "type": "commit"}}
+{"return": {}}
 {"error": {"class": "GenericError", "desc": "Node 'drv0' is busy: block device 
is in use by block job: commit"}}
 {"return": {}}
 {"timestamp": {"seconds":  TIMESTAMP, "microseconds":  TIMESTAMP}, "event": 
"JOB_STATUS_CHANGE", "data": {"status": "waiting", "id": "job0"}}
Failures: 141
Failed 1 of 1 tests

IIRC this was working fine two months ago (at least I don't remember
having seen it at that point in time).


reply via email to

[Prev in Thread] Current Thread [Next in Thread]