From: tu bo <tubo@linux.vnet.ibm.com>
To: Max Reitz <mreitz@redhat.com>, qemu-devel@nongnu.org
Cc: kwolf@redhat.com, mimu@linux.vnet.ibm.com, armbru@redhat.com,
silbe@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [PATCH v2 4/4] qemu-iotests: disable VNC server for test 120
Date: Thu, 19 Nov 2015 15:06:34 +0800 [thread overview]
Message-ID: <564D74FA.3030505@linux.vnet.ibm.com> (raw)
In-Reply-To: <564CADCE.30303@redhat.com>
Hi Max:
On 11/19/2015 12:56 AM, Max Reitz wrote:
> On 04.11.2015 03:26, Bo Tu wrote:
>> Ever since qemu-iotest 120 was introduced, its expected output didn't
>> include the output from the built-in VNC server:
>>
>> QA output created by 120
>> Formatting 'TEST_DIR/t.IMGFMT', fmt=IMGFMT size=67108864
>> QMP_VERSION
>> +VNC server running on `::1:5900'
>> {"return": {}}
>> wrote 65536/65536 bytes at offset 0
>> 64 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
>>
>> Since some architectures do not even have a graphical console, we just
>> pass -nographic to avoid the output.
>>
>> Fixes: a68197ff5b11 ("iotests: Add tests for overriding
>> BDRV_O_PROTOCOL")
>>
>> Reviewed-by: Sascha Silbe <silbe@linux.vnet.ibm.com>
>> Signed-off-by: Bo Tu <tubo@linux.vnet.ibm.com>
>> ---
>> tests/qemu-iotests/120 | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/tests/qemu-iotests/120 b/tests/qemu-iotests/120
>> index 9f13078..fb69efd 100755
>> --- a/tests/qemu-iotests/120
>> +++ b/tests/qemu-iotests/120
>> @@ -49,7 +49,7 @@ echo "{'execute': 'qmp_capabilities'}
>> {'execute': 'human-monitor-command',
>> 'arguments': {'command-line': 'qemu-io drv \"write -P 42 0 64k\"'}}
>> {'execute': 'quit'}" \
>> - | $QEMU -qmp stdio -nodefaults \
>> + | $QEMU -qmp stdio -nodefaults -nographic \
>> -drive id=drv,if=none,file="$TEST_IMG",driver=raw,file.driver=$IMGFMT \
>> | _filter_qmp | _filter_qemu_io
>> $QEMU_IO -c 'read -P 42 0 64k' "$TEST_IMG" | _filter_qemu_io
>
> Looks good, but I think we need the same for 119.
I agree with you that 119 need to add the parameter of "-nographic" at
line 53.
52 | $QEMU -drive id=drv,if=none,file="$TEST_IMG",driver=nbd \
53 -qmp stdio -nodefaults \
>
> Max
>
prev parent reply other threads:[~2015-11-19 7:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-04 2:26 [Qemu-devel] [PATCH v2 0/4] Update tests/qemu-iotests failing cases for the s390 platform Bo Tu
2015-11-04 2:26 ` [Qemu-devel] [PATCH v2 1/4] qemu-iotests: refine common.config Bo Tu
2015-11-18 16:45 ` Max Reitz
2015-11-19 5:58 ` tu bo
2015-11-04 2:26 ` [Qemu-devel] [PATCH v2 2/4] qemu-iotests: s390x: fix test 051 Bo Tu
2015-11-18 16:52 ` Max Reitz
2015-11-19 7:28 ` tu bo
2015-11-20 16:24 ` Max Reitz
2015-11-23 3:34 ` tu bo
2015-11-24 21:17 ` Sascha Silbe
2015-11-25 15:41 ` Max Reitz
2015-11-26 10:15 ` tu bo
2015-11-04 2:26 ` [Qemu-devel] [PATCH v2 3/4] qemu-iotests: s390x: fix test 068 Bo Tu
2015-11-18 16:57 ` Max Reitz
2015-11-04 2:26 ` [Qemu-devel] [PATCH v2 4/4] qemu-iotests: disable VNC server for test 120 Bo Tu
2015-11-18 16:56 ` Max Reitz
2015-11-19 7:06 ` tu bo [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=564D74FA.3030505@linux.vnet.ibm.com \
--to=tubo@linux.vnet.ibm.com \
--cc=armbru@redhat.com \
--cc=kwolf@redhat.com \
--cc=mimu@linux.vnet.ibm.com \
--cc=mreitz@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=silbe@linux.vnet.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.