From: Max Reitz <mreitz@redhat.com>
To: Thomas Huth <thuth@redhat.com>, QEMU Developers <qemu-devel@nongnu.org>
Cc: Kevin Wolf <kwolf@redhat.com>, Qemu-block <qemu-block@nongnu.org>
Subject: Re: iotest 041 is failing with -qed
Date: Wed, 17 Jun 2020 08:42:17 +0200 [thread overview]
Message-ID: <8f918615-1666-dd8e-1815-98ab224ec610@redhat.com> (raw)
In-Reply-To: <900ebe8c-ac9e-a355-b068-41735863dce4@redhat.com>
[-- Attachment #1.1: Type: text/plain, Size: 3388 bytes --]
On 17.06.20 08:18, Thomas Huth wrote:
>
> Hi!
>
> I just noticed that iotest 041 is failing with -qed:
>
> $ ./check -qed 041
> QEMU --
> "tests/qemu-iotests/../../x86_64-softmmu/qemu-system-x86_64" -nodefaults
> -display none -accel qtest
> QEMU_IMG -- "tests/qemu-iotests/../../qemu-img"
> QEMU_IO -- "tests/qemu-iotests/../../qemu-io" --cache writeback
> --aio threads -f qed
> QEMU_NBD -- "tests/qemu-iotests/../../qemu-nbd"
> IMGFMT -- qed
> IMGPROTO -- file
> PLATFORM -- Linux/x86_64 thuth 4.18.0-80.11.2.el8_0.x86_64
> TEST_DIR -- tests/qemu-iotests/scratch
> SOCK_DIR -- /tmp/tmp.Fgwzwl4EoG
> SOCKET_SCM_HELPER -- tests/qemu-iotests/socket_scm_helper
>
> 041 fail [08:12:36] [08:13:09] (last: 31s) output
> mismatch (see 041.out.bad)
> --- tests/qemu-iotests/041.out 2020-06-15 14:11:05.389400610 +0200
> +++ tests/qemu-iotests/041.out.bad 2020-06-17 08:13:09.205195987 +0200
> @@ -1,5 +1,33 @@
> -........................................................................................................
> +........................................F............F..................................................
> +======================================================================
> +FAIL: test_small_target (__main__.TestSingleBlockdev)
> +----------------------------------------------------------------------
> +Traceback (most recent call last):
> + File "041", line 281, in test_small_target
> + self.do_test_target_size(self.image_len // 2)
> + File "041", line 270, in do_test_target_size
> + self.assert_qmp(result, 'return', {})
> + File "tests/qemu-iotests/iotests.py", line 848, in assert_qmp
> + result = self.dictpath(d, path)
> + File "tests/qemu-iotests/iotests.py", line 822, in dictpath
> + self.fail(f'failed path traversal for "{path}" in "{d}"')
> +AssertionError: failed path traversal for "return" in "{'error':
> {'class': 'GenericError', 'desc': 'Shrinking images is currently not
> supported'}}"
> +
> +======================================================================
> +FAIL: test_small_target (__main__.TestSingleBlockdevUnalignedLength)
> +----------------------------------------------------------------------
> +Traceback (most recent call last):
> + File "041", line 281, in test_small_target
> + self.do_test_target_size(self.image_len // 2)
> + File "041", line 270, in do_test_target_size
> + self.assert_qmp(result, 'return', {})
> + File "tests/qemu-iotests/iotests.py", line 848, in assert_qmp
> + result = self.dictpath(d, path)
> + File "tests/qemu-iotests/iotests.py", line 822, in dictpath
> + self.fail(f'failed path traversal for "{path}" in "{d}"')
> +AssertionError: failed path traversal for "return" in "{'error':
> {'class': 'GenericError', 'desc': 'Shrinking images is currently not
> supported'}}"
> +
> ----------------------------------------------------------------------
> Ran 104 tests
>
> -OK
> +FAILED (failures=2)
> Failures: 041
> Failed 1 of 1 iotests
>
> Is it a known problem already?
Well, FWIW, I knew of it, but didn’t get around to doing anything about
it yet.
Thanks for reporting it anyway, now I have better justification to do
something about it. :) (And of course in case I would have missed it.)
Max
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2020-06-17 6:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-17 6:18 iotest 041 is failing with -qed Thomas Huth
2020-06-17 6:42 ` 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=8f918615-1666-dd8e-1815-98ab224ec610@redhat.com \
--to=mreitz@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--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).