[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PATCH v3 8/8] RFC iotests: Disable 236 and 238 on Open
From: |
John Snow |
Subject: |
Re: [Qemu-devel] [PATCH v3 8/8] RFC iotests: Disable 236 and 238 on OpenBSD |
Date: |
Mon, 4 Feb 2019 19:33:35 -0500 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.4.0 |
On 2/4/19 7:18 PM, Philippe Mathieu-Daudé wrote:
> These tests explode on OpenBSD:
>
> $ gmake check-block
> [...]
> 238 [17:16:09] [17:16:09] [failed, exit status 1] - output
> mismatch (see 238.out.bad)
> --- /tmp/qemu-test.VKNS07/tests/qemu-iotests/238.out Tue Jan 29 17:09:03
> 2019
> +++ /tmp/qemu-test.VKNS07/tests/qemu-iotests/238.out.bad Tue Jan 29
> 17:16:09 2019
> @@ -1,6 +1,14 @@
> -{"return": {}}
> -{"return": {}}
> -{"return": {}}
> -{"return": {}}
> -{"return": {}}
> -{"return": {}}
> +Traceback (most recent call last):
> + File "238", line 37, in <module>
> + vm.launch()
> + File "/tmp/qemu-test.VKNS07/tests/qemu-iotests/../../scripts/qemu.py",
> line 295, in launch
> + self._launch()
> + File "/tmp/qemu-test.VKNS07/tests/qemu-iotests/../../scripts/qemu.py",
> line 321, in _launch
> + self._post_launch()
> + File "/tmp/qemu-test.VKNS07/tests/qemu-iotests/../../scripts/qemu.py",
> line 266, in _post_launch
> + self._qmp.accept()
> + File
> "/tmp/qemu-test.VKNS07/tests/qemu-iotests/../../scripts/qmp/qmp.py", line
> 157, in accept
> + return self.__negotiate_capabilities()
> + File
> "/tmp/qemu-test.VKNS07/tests/qemu-iotests/../../scripts/qmp/qmp.py", line 73,
> in __negotiate_capabilities
> + raise QMPConnectError
> +qmp.qmp.QMPConnectError
>
> Signed-off-by: Philippe Mathieu-Daudé <address@hidden>
> ---
> This might be due to these tests requiring KVM?...
> Maybe we need a has_kvm argument to iotests.verify_platform()?
Uhhh, 236 shouldn't be doing anything fancy. It does boot a VM, but so
does 237, 222, 219, 218, 216, ...
I actually don't know what this would be failing. Any chance to look at
the core dump QEMU is leaving behind?
> ---
> tests/qemu-iotests/236 | 1 +
> tests/qemu-iotests/238 | 2 ++
> 2 files changed, 3 insertions(+)
>
> diff --git a/tests/qemu-iotests/236 b/tests/qemu-iotests/236
> index 79a6381f8e..b98df35ca4 100755
> --- a/tests/qemu-iotests/236
> +++ b/tests/qemu-iotests/236
> @@ -23,6 +23,7 @@ import iotests
> from iotests import log
>
> iotests.verify_image_format(supported_fmts=['generic'])
> +iotests.verify_platform(unsupported_oses=['openbsd']) # FIXME
> size = 64 * 1024 * 1024
> granularity = 64 * 1024
>
> diff --git a/tests/qemu-iotests/238 b/tests/qemu-iotests/238
> index f81ee1112f..c62ff9a6dc 100755
> --- a/tests/qemu-iotests/238
> +++ b/tests/qemu-iotests/238
> @@ -23,6 +23,8 @@ import os
> import iotests
> from iotests import log
>
> +iotests.verify_platform(unsupported_oses=['openbsd']) # FIXME
> +
> sys.path.append(os.path.join(os.path.dirname(__file__), '..', '..',
> 'scripts'))
>
> from qemu import QEMUMachine
>
- [Qemu-devel] [PATCH v3 0/8] OpenBSD: Block layer fixes (was 'Enable qtesting'), Philippe Mathieu-Daudé, 2019/02/04
- [Qemu-devel] [PATCH v3 2/8] qemu-iotests: Add dependency to qemu-nbd tool, Philippe Mathieu-Daudé, 2019/02/04
- [Qemu-devel] [PATCH v3 4/8] qemu-iotests: Ensure GNU sed is used, Philippe Mathieu-Daudé, 2019/02/04
- [Qemu-devel] [PATCH v3 5/8] iotests: Let verify_platform() check for unsupported platforms, Philippe Mathieu-Daudé, 2019/02/04
- [Qemu-devel] [PATCH v3 6/8] RFC iotests: Disable 208 on OpenBSD, Philippe Mathieu-Daudé, 2019/02/04
- [Qemu-devel] [PATCH v3 7/8] RFC iotests: Disable 209 on OpenBSD, Philippe Mathieu-Daudé, 2019/02/04
- [Qemu-devel] [PATCH v3 3/8] qemu-iotests: Improve portability by searching bash in the $PATH, Philippe Mathieu-Daudé, 2019/02/04
- [Qemu-devel] [PATCH v3 8/8] RFC iotests: Disable 236 and 238 on OpenBSD, Philippe Mathieu-Daudé, 2019/02/04
- [Qemu-devel] [PATCH v3 1/8] ahci-test: Add dependency to qemu-img tool, Philippe Mathieu-Daudé, 2019/02/04
Re: [Qemu-devel] [PATCH v3 0/8] OpenBSD: Block layer fixes (was 'Enable qtesting'), no-reply, 2019/02/04