From: Max Reitz <mreitz@redhat.com>
To: Thomas Huth <thuth@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>,
Qemu-block <qemu-block@nongnu.org>, Kevin Wolf <kwolf@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] iotest 141 fails with qed
Date: Wed, 17 Jul 2019 14:40:49 +0200 [thread overview]
Message-ID: <9fad7a25-a02b-ddca-2543-d4305f40c0db@redhat.com> (raw)
In-Reply-To: <bb3c5cc1-6aa6-ccae-455d-b9b4bf6479a5@redhat.com>
[-- Attachment #1.1: Type: text/plain, Size: 2356 bytes --]
On 17.07.19 14:35, Thomas Huth wrote:
> FWIW, I've got a new iotest failure with current master branch:
>
> $ ./check -qed 141
> QEMU -- "/tmp/qemu/tests/qemu-iotests/../../x86_64-softmmu/qemu-system-x86_64" -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 +0200
> @@ -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).
You are correct.
Vladimir proposed a fix for this:
https://lists.nongnu.org/archive/html/qemu-block/2019-05/msg00982.html
But he never sent a patch, so I guess I’ll have to make it a patch, then.
Max
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2019-07-17 12:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-17 12:35 [Qemu-devel] iotest 141 fails with qed Thomas Huth
2019-07-17 12:40 ` Max Reitz [this message]
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=9fad7a25-a02b-ddca-2543-d4305f40c0db@redhat.com \
--to=mreitz@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=thuth@redhat.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).