From: John Snow
verify_platform will check an explicit whitelist and blacklist instead.
The default will now be assumed to be allowed to run anywhere.
For tests that do not specify their platforms explicitly, this has the effect of
enabling these tests on non-linux platforms. For tests that
for iothreads. For
migration, let's enable 091, 181, 183, and 203 (which also tests
iothreads).
Reviewed-by: Max Reitz
Signed-off-by: Thomas Huth
---
tests/qemu-iotests/group | 18 +-
1 file changed, 9 insertions(+), 9 deletions(-)
diff --git a/tests/qemu-iotests/group b/tests/qemu
041 works fine on Linux, FreeBSD, NetBSD and OpenBSD, but fails on macOS.
Let's mark it as only supported on the systems where we know that it is
working fine.
Signed-off-by: Thomas Huth
---
tests/qemu-iotests/041 | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/tests/qemu
From: John Snow
verify_platform will check an explicit whitelist and blacklist instead.
The default will now be assumed to be allowed to run anywhere.
For tests that do not specify their platforms explicitly, this has the effect of
enabling these tests on non-linux platforms. For tests that
handle 0" error.
Let's mark it as supported only on systems where the test is working
fine (i.e. Linux, FreeBSD and NetBSD).
Signed-off-by: Thomas Huth
---
tests/qemu-iotests/183 | 1 +
1 file changed, 1 insertion(+)
diff --git a/tests/qemu-iotests/183 b/tests/qemu-iotests/183
index bced83fae
every test (which does not sound very appealing), let's rather add
a check for this at the top level in the check-block.sh script instead
(so that it is possible to run "make check" without the "check-block"
part for qemu-system-tricore for example).
Reviewed-by: Max Reitz
Signed-o
for iothreads. For
migration, let's enable 091, 181, and 203 (which also tests iothreads).
Reviewed-by: Max Reitz
Signed-off-by: Thomas Huth
---
tests/qemu-iotests/group | 16
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/tests/qemu-iotests/group b/tests/qemu-iotests
roup so
that it does not gate the pull requests.
Reviewed-by: John Snow
Signed-off-by: Thomas Huth
---
tests/qemu-iotests/group | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tests/qemu-iotests/group b/tests/qemu-iotests/group
index 33b499ed41..4596497bce 100644
--- a/tests/qemu
erd's patches for creating NetBSD VM images)
- Use 'openbsd' instead of 'openbsd6'
- Use 'grep -q' instead of 'grep' for grep'ing silently
- Added the patch to disable 130 from the "auto" group
John Snow (1):
iotests: remove 'linux' from default supported platforms
Thomas Huth (5):
041 works fine on Linux, FreeBSD, NetBSD and OpenBSD, but fails on macOS.
Let's mark it as only supported on the systems where we know that it is
working fine.
Signed-off-by: Thomas Huth
---
tests/qemu-iotests/041 | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/tests/qemu
On 22/10/2019 13.39, Alex Bennée wrote:
>
> Thomas Huth writes:
>
>> On 22/10/2019 09.21, Thomas Huth wrote:
>>> As discussed here:
>>>
>>> https://lists.gnu.org/archive/html/qemu-devel/2019-10/msg00697.html
>>>
>>> and here:
&g
s/virtio.c | 7 +++
> 2 files changed, 8 insertions(+)
Reviewed-by: Thomas Huth
anged, 476 insertions(+), 1 deletion(-)
> create mode 100644 tests/libqos/virtio-pci-modern.h
> create mode 100644 tests/libqos/virtio-pci-modern.c
Acked-by: Thomas Huth
n Hajnoczi
> ---
> tests/libqos/virtio-9p.c | 6 ++
> 1 file changed, 6 insertions(+)
Reviewed-by: Thomas Huth"
-test.c | 8 ++++
> 1 file changed, 8 insertions(+)
Reviewed-by: Thomas Huth"
--
> tests/libqos/virtio.c | 18 +++++-
> 1 file changed, 17 insertions(+), 1 deletion(-)
Reviewed-by: Thomas Huth"
On 22/10/2019 09.21, Thomas Huth wrote:
> As discussed here:
>
> https://lists.gnu.org/archive/html/qemu-devel/2019-10/msg00697.html
>
> and here:
>
> https://lists.gnu.org/archive/html/qemu-devel/2019-10/msg01388.html
>
> it would be good to have some mo
issue, so for the time being, let's disable it from the "auto" group so
that it does not gate the pull requests.
Signed-off-by: Thomas Huth
---
tests/qemu-iotests/group | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tests/qemu-iotests/group b/tests/qemu-iotests/gr
e"
>
> # get standard environment, filters and checks
> . ./common.rc
>
Reviewed-by: Thomas Huth
On 17/10/2019 15.31, Max Reitz wrote:
> In addition, drop the nbd_unix_socket assignment in 241 because it does
> not really do anything.
Right, common.nbd is included afterwards, so it gets overwritten.
Reviewed-by: Thomas Huth
On 17/10/2019 15.31, Max Reitz wrote:
> Signed-off-by: Max Reitz
> Reviewed-by: Eric Blake
> ---
> tests/qemu-iotests/192 | 4 ++--
> tests/qemu-iotests/192.out | 2 +-
> 2 files changed, 3 insertions(+), 3 deletions(-)
Reviewed-by: Thomas Huth
On 17/10/2019 15.31, Max Reitz wrote:
> Signed-off-by: Max Reitz
> Reviewed-by: Eric Blake
> ---
> tests/qemu-iotests/240 | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
Reviewed-by: Thomas Huth
On 17/10/2019 15.31, Max Reitz wrote:
> Signed-off-by: Max Reitz
> Reviewed-by: Eric Blake
> ---
> tests/qemu-iotests/common.filter | 6 +-
> 1 file changed, 5 insertions(+), 1 deletion(-)
Reviewed-by: Thomas Huth
nbd_sock = os.path.join(iotests.sock_dir, 'nbd_sock')
> nbd_uri = 'nbd+unix:///exp?socket=' + nbd_sock
> disk = os.path.join(iotests.test_dir, 'disk')
Reviewed-by: Thomas Huth
\
> -e 's#\(foo\|PORT/\?\|.sock\): Failed to .*$#\1#'
> }
>
Reviewed-by: Thomas Huth
On 17/10/2019 15.31, Max Reitz wrote:
> Signed-off-by: Max Reitz
> Reviewed-by: Eric Blake
> ---
> tests/qemu-iotests/267 | 4 ++--
> tests/qemu-iotests/267.out | 2 +-
> 2 files changed, 3 insertions(+), 3 deletions(-)
Reviewed-by: Thomas Huth
On 17/10/2019 15.31, Max Reitz wrote:
> Signed-off-by: Max Reitz
> Reviewed-by: Eric Blake
> ---
> tests/qemu-iotests/223 | 14 +++---
> 1 file changed, 7 insertions(+), 7 deletions(-)
Reviewed-by: Thomas Huth
On 22/10/2019 17.48, Stefan Hajnoczi wrote:
> On Mon, Oct 21, 2019 at 02:15:53PM +0200, Thomas Huth wrote:
>> On 19/10/2019 08.38, Stefan Hajnoczi wrote:
>>> According to VIRTIO 1.1 "3.1.1 Driver Requirements: Device
>>> Initialization", configuration sp
On 22/10/2019 15.48, Alex Bennée wrote:
>
> Max Reitz writes:
>
>> On 22.10.19 15:11, Alex Bennée wrote:
>>>
>>> Thomas Huth writes:
>>>
>>>> As discussed here:
>>>>
>>>> https://lists.gnu.org/archive/html/qemu-de
In certain environments like restricted containers, we can not create
huge test images. To be able to use "make check" in such container
environments, too, let's skip the hd-geo-test instead of failing when
the test images could not be created.
Signed-off-by: Thomas Huth
---
tests/hd-
,
so we can not use the global list of packages to install, but have to
provide individual package lists instead.
Signed-off-by: Thomas Huth
---
.travis.yml | 83 +
1 file changed, 83 insertions(+)
diff --git a/.travis.yml b/.travis.yml
index
test-util-filemonitor fails in restricted non-x86 Travis containers
since they apparently blacklisted some required system calls there.
Let's simply skip the test if we detect such an environment.
Signed-off-by: Thomas Huth
---
tests/test-util-filemonitor.c | 11 +++
1 file changed, 11
-off-by: Thomas Huth
---
.travis.yml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/.travis.yml b/.travis.yml
index b9a026c8ee..c09b6a0014 100644
--- a/.travis.yml
+++ b/.travis.yml
@@ -79,7 +79,7 @@ env:
- BASE_CONFIG="--disable-docs --disable-tools"
- TEST
Test 060 fails in the arm64, s390x and ppc64le LXD containers, which
apparently do not allow large files to be created. The repair process
in test 060 creates a file of 64 GiB, so test first whether such large
files are possible and skip the test if that's not the case.
Signed-off-by: Thomas Huth
hits the 50 minutes
timeout otherwise.
For the curious, here's a test run (non-x86 at the end of the page):
https://travis-ci.com/huth/qemu/jobs/258095792
Thomas
Alex Bennée (1):
travis.yml: drop 32 bit systems from MAIN_SOFTMMU_TARGETS
Thomas Huth (5):
iotests: Skip test 060
Test 079 fails in the arm64, s390x and ppc64le LXD containers, which
apparently do not allow large files to be created. Test 079 tries to
create a 4G sparse file, so check first whether we can really create
such files before executing the test.
Signed-off-by: Thomas Huth
---
tests/qemu-iotests
On 19/11/2019 18.50, Daniel P. Berrangé wrote:
> On Tue, Nov 19, 2019 at 06:38:20PM +0100, Philippe Mathieu-Daudé wrote:
>> On 11/19/19 6:34 PM, Thomas Huth wrote:
>>> On 19/11/2019 18.29, Philippe Mathieu-Daudé wrote:
>>>> On 11/19/19 6:08 PM, Thomas Huth wrote:
>
On 19/11/2019 18.29, Philippe Mathieu-Daudé wrote:
> On 11/19/19 6:08 PM, Thomas Huth wrote:
>> Test 079 fails in the arm64, s390x and ppc64le LXD containers, which
>> apparently do not allow large files to be created. Test 079 tries to
>> create a 4G sparse file, so check
On 25/11/2019 11.28, Alex Bennée wrote:
Alex Bennée writes:
Thomas Huth writes:
Travis recently added build hosts for arm64, ppc64le and s390x, so
this is a welcome addition to our Travis testing matrix.
Unfortunately, the builds are running in quite restricted LXD containers
On 24/10/2019 13.14, Alex Bennée wrote:
Thomas Huth writes:
According to Max, it would be good to have a test for iothreads and
migration. 127 and 256 seem to be good candidates for iothreads. For
migration, let's enable 091, 181, and 203 (which also tests iothreads).
@@ -112,7 +112,7
uardo has
re-activated Gerd's patches for creating NetBSD VM images)
- Use 'openbsd' instead of 'openbsd6'
- Use 'grep -q' instead of 'grep' for grep'ing silently
- Added the patch to disable 130 from the "auto" group
John Snow (1):
iotests: remove 'linux' from default supported pl
in iotest 267 - it has been added to
the "auto" group already, but requires virtio-blk and thus currently
fails with qemu-system-tricore for example. Let's also add aproper
check there.
Signed-off-by: Thomas Huth
---
tests/qemu-iotests/127 | 2 ++
tests/qemu-iotests/267
From: John Snow
verify_platform will check an explicit whitelist and blacklist instead.
The default will now be assumed to be allowed to run anywhere.
For tests that do not specify their platforms explicitly, this has the effect of
enabling these tests on non-linux platforms. For tests that
first whether we can really create such files before
executing the test.
Signed-off-by: Thomas Huth
---
tests/qemu-iotests/079 | 3 +++
1 file changed, 3 insertions(+)
diff --git a/tests/qemu-iotests/079 b/tests/qemu-iotests/079
index 81f0c21f53..78536d3bbf 100755
--- a/tests/qemu-iotests/079
checks in the iotests 005 and 220 with this function.
Signed-off-by: Thomas Huth
---
tests/qemu-iotests/005 | 5 +
tests/qemu-iotests/220 | 6 ++
tests/qemu-iotests/common.rc | 10 ++
3 files changed, 13 insertions(+), 8 deletions(-)
diff --git a/tests/qemu-iotests/005
041 works fine on Linux, FreeBSD, NetBSD and OpenBSD, but fails on macOS.
Let's mark it as only supported on the systems where we know that it is
working fine.
Signed-off-by: Thomas Huth
---
tests/qemu-iotests/041 | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/tests/qemu
every
test (which does not sound very appealing), let's rather add a check for
this a central spot in the "check" script instead (so that it is still
possible to run "make check" for qemu-system-tricore for example).
Signed-off-by: Thomas Huth
---
tests/qemu-iotests/check |
for iothreads. For
migration, let's enable 181 and 203 (which also tests iothreads).
(091 would be a good candidate for migration, too, but Alex Bennée
reported that this test fails on ZFS file systems, so it can't be
included yet)
Signed-off-by: Thomas Huth
---
tests/qemu-iotests/group | 14
and skip the test if that's not the case.
Signed-off-by: Thomas Huth
---
tests/qemu-iotests/060 | 3 +++
1 file changed, 3 insertions(+)
diff --git a/tests/qemu-iotests/060 b/tests/qemu-iotests/060
index b91d8321bb..d96f17a484 100755
--- a/tests/qemu-iotests/060
+++ b/tests/qemu-iotests/060
.
Thomas Huth (3):
iotests: Provide a function for checking the creation of huge files
iotests: Skip test 060 if it is not possible to create large files
iotests: Skip test 079 if it is not possible to create large files
tests/qemu-iotests/005 | 5 +
tests/qemu-iotests/060 | 3
On 24/09/2019 20.49, John Snow wrote:
> Nobody was making movement on this patch series, and in response to Max
> acking the whole series, I was just going to send a pull request for the
> whole thing and see who barked, because nobody likes or hates this
> series enough to offer any feedback.
>
On 04/10/2019 14.44, Max Reitz wrote:
> On 04.10.19 12:19, Kevin Wolf wrote:
>> Am 02.10.2019 um 19:47 hat Max Reitz geschrieben:
>>> On 02.10.19 18:44, Kevin Wolf wrote:
Am 02.10.2019 um 13:57 hat Max Reitz geschrieben:
> It usually worked fine for me because it’s rather rare that
On 07/10/2019 14.52, Max Reitz wrote:
> On 07.10.19 14:16, Thomas Huth wrote:
>> On 04/10/2019 14.44, Max Reitz wrote:
>>> On 04.10.19 12:19, Kevin Wolf wrote:
>>>> Am 02.10.2019 um 19:47 hat Max Reitz geschrieben:
>>>>> On 02.10.19 18:44, Kevin Wolf
On 07/10/2019 15.11, Thomas Huth wrote:
> On 07/10/2019 14.52, Max Reitz wrote:
>> On 07.10.19 14:16, Thomas Huth wrote:
>>> On 04/10/2019 14.44, Max Reitz wrote:
>>>> On 04.10.19 12:19, Kevin Wolf wrote:
>>>>> Am 02.10.2019 um 19:47 hat Max Reitz gesc
eter Krempa
> Signed-off-by: John Snow
> ---
> qemu-deprecated.texi | 5 +
> hw/ide/qdev.c | 3 +++
> tests/qemu-iotests/051.pc.out | 6 --
> 3 files changed, 12 insertions(+), 2 deletions(-)
Reviewed-by: Thomas Huth
achine.py| 15 ---
> python/qemu/qtest.py | 9 ++---
> tests/qemu-iotests/iotests.py | 4 +++-
> 3 files changed, 21 insertions(+), 7 deletions(-)
Reviewed-by: Thomas Huth
On 10/10/2019 17.24, Max Reitz wrote:
> Hi,
>
> Perhaps the main reason we cannot run important tests such as 041 in CI
> is that when they care Unix sockets in $TEST_DIR, the path may become
> too long to connect to them.
>
> To get by this problem, this series lets the check script create a
On 10/10/2019 17.24, Max Reitz wrote:
> Signed-off-by: Max Reitz
> ---
> tests/qemu-iotests/083 | 6 +++---
> tests/qemu-iotests/083.out | 34 +-
> 2 files changed, 20 insertions(+), 20 deletions(-)
Reviewed-by: Thomas Huth
On 10/10/2019 17.24, Max Reitz wrote:
> Signed-off-by: Max Reitz
> ---
> tests/qemu-iotests/181 | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Reviewed-by: Thomas Huth
On 10/10/2019 17.24, Max Reitz wrote:
> Signed-off-by: Max Reitz
> ---
> tests/qemu-iotests/147 | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Reviewed-by: Thomas Huth
On 10/10/2019 17.24, Max Reitz wrote:
> Signed-off-by: Max Reitz
> ---
> tests/qemu-iotests/182 | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
Reviewed-by: Thomas Huth
On 11/10/2019 09.54, Max Reitz wrote:
> On 10.10.19 20:42, Eric Blake wrote:
>> On 10/10/19 10:24 AM, Max Reitz wrote:
>>> Signed-off-by: Max Reitz
>>> ---
>>> tests/qemu-iotests/common.filter | 8 ++--
>>> 1 file changed, 6 insertions(+), 2 deletions(-)
>>>
>>> diff --git
On 11/10/2019 10.03, Max Reitz wrote:
> On 11.10.19 09:27, Thomas Huth wrote:
>> On 10/10/2019 17.24, Max Reitz wrote:
>>> Hi,
>>>
>>> Perhaps the main reason we cannot run important tests such as 041 in CI
>>> is that when they care Unix sockets i
On 10/10/2019 17.24, Max Reitz wrote:
> Signed-off-by: Max Reitz
> ---
> tests/qemu-iotests/140 | 8
> tests/qemu-iotests/140.out | 2 +-
> 2 files changed, 5 insertions(+), 5 deletions(-)
Reviewed-by: Thomas Huth
On 10/10/2019 17.24, Max Reitz wrote:
> Signed-off-by: Max Reitz
> ---
> tests/qemu-iotests/143 | 6 +++---
> tests/qemu-iotests/143.out | 2 +-
> 2 files changed, 4 insertions(+), 4 deletions(-)
Reviewed-by: Thomas Huth
On 10/10/2019 17.24, Max Reitz wrote:
> Signed-off-by: Max Reitz
> ---
> tests/qemu-iotests/183 | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Reviewed-by: Thomas Huth
On 11/10/2019 11.07, Max Reitz wrote:
> For long test image paths, the order of the "Formatting" line and the
> "(qemu)" prompt after a drive_backup HMP command may be reversed. It is
> not well-defined anyway, so just silence everything and wait until we
> get a
for iothreads. For
migration, let's enable 091, 181, 183, and 203 (which also tests
iothreads).
Signed-off-by: Thomas Huth
---
tests/qemu-iotests/group | 18 +-
1 file changed, 9 insertions(+), 9 deletions(-)
diff --git a/tests/qemu-iotests/group b/tests/qemu-iotests/group
index
From: John Snow
verify_platform will check an explicit whitelist and blacklist instead.
The default will now be assumed to be allowed to run anywhere.
For tests that do not specify their platforms explicitly, this has the effect of
enabling these tests on non-linux platforms. For tests that
When running 183 in Cirrus-CI on macOS, or with our vm-build-openbsd
target, it fails with an "Timeout waiting for return on handle 0" error.
Let's mark it as supported only on systems where the test is working
fine (i.e. Linux and FreeBSD).
Signed-off-by: Thomas Huth
---
tests/qe
every test (which does not sound very appealing), let's rather add
a check for this at the top level in the check-block.sh script instead
(so that it is possible to run "make check" without the "check-block"
part for qemu-system-tricore for example).
Signed-off-by: Thomas Huth
041 works fine on Linux, FreeBSD and OpenBSD, so let's mark it as
only supported on these systems.
Signed-off-by: Thomas Huth
---
tests/qemu-iotests/041 | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/tests/qemu-iotests/041 b/tests/qemu-iotests/041
index 8568426311
with binaries like qemu-system-tricore anymore. But since the iotests
were not very useful with such binaries anyway, I think it's ok now
if we skip them there.
Based-on: 20191010152457.17713-1-mre...@redhat.com
John Snow (1):
iotests: remove 'linux' from default supported platforms
Thomas Huth
On 14/10/2019 13.21, Kevin Wolf wrote:
> Am 11.10.2019 um 16:50 hat Thomas Huth geschrieben:
>> The next patch is going to add some python-based tests to the "auto"
>> group, and these tests require virtio-blk to work properly. Running
>> iotests without virtio-bl
Formatting" to being greppable at all after "read"-ing it (if the
> prompt injects an IFS character into the "Formatting" string).
>
> So just wait until we get a prompt. At that point, the block job must
> have been started, so "info block-jobs" will onl
The python code already contains a possibility to skip tests if the
corresponding driver is not available in the qemu binary - use it
in more spots to avoid that the tests are failing if the driver has
been disabled.
Signed-off-by: Thomas Huth
---
v2: Thanks to Max' "iotests: Allow ski
Test 051 should be skipped if nbd is not available, and 267 should
be skipped if copy-on-read is not enabled.
Signed-off-by: Thomas Huth
---
tests/qemu-iotests/051 | 1 +
tests/qemu-iotests/267 | 1 +
2 files changed, 2 insertions(+)
diff --git a/tests/qemu-iotests/051 b/tests/qemu-iotests/051
img_info
> --backing-chain --image-opts \
> +| _filter_img_info | grep -v 'backing file format'
>
> # success, all done
> echo "*** done"
>
This fixes the problems with "check -qed 279" and "check -vmdk 279" for me.
Tested-by: Thomas Huth
Commit d9df28e7b07 ("iotests: check whitelisted formats") added the
modern @iotests.skip_if_unsupported() to the functions in this test,
so we don't need the old explicit test here anymore.
Signed-off-by: Thomas Huth
---
tests/qemu-iotests/139 | 3 ---
1 file changed, 3 deletions(-)
On 30/01/2020 23.31, Philippe Mathieu-Daudé wrote:
> On 1/21/20 10:52 AM, Thomas Huth wrote:
>> We are going to enable some of the python-based tests in the "auto"
>> group,
>> and these tests require virtio-blk to work properly. Running iotests
>> without vir
On 09/01/2020 16.03, Vladimir Sementsov-Ogievskiy wrote:
> 06.01.2020 20:15, Max Reitz wrote:
>> Misc
>>
>>
>> The Wiki’s TODO list is horribly outdated. What should we do about
>> it? Maybe archive it and start a new one? (Most of the things on the
>> current list are either done or we
iotests.supports_quorum() - and which were apparently not
working as expected since the tests aborted instead of being skipped
when "quorum" was missing in the QEMU binary.
Signed-off-by: Thomas Huth
---
v3:
- Remove the old iotests.supports_quorum()-based tests
- Check for "t
The qtests have recently been moved to a separate subdirectory, so
the paths that are mentioned in the documentation have to be adjusted
accordingly. And some of the iotests are now always run as part of
"make check", so this information has to be adjusted here, too.
Signed-off-by: T
On 20/01/2020 15.50, Max Reitz wrote:
> On 02.12.19 11:10, Thomas Huth wrote:
>> We are going to enable some of the python-based tests in the "auto" group,
>> and these tests require virtio-blk to work properly. Running iotests
>> without virtio-blk likely does not
On 20/01/2020 15.36, Max Reitz wrote:
> On 02.12.19 11:10, Thomas Huth wrote:
>> In the long term, we might want to add test 183 to the "auto" group
>> (but it still fails occasionally, so we cannot do that yet). However,
>> when running 183 in Cirrus-CI on macO
'grep -q' instead of 'grep' for grep'ing silently
- Added the patch to disable 130 from the "auto" group
John Snow (1):
iotests: remove 'linux' from default supported platforms
Thomas Huth (5):
iotests: Test 041 only works on certain systems
iotests: Test 183 does not work on macOS
From: John Snow
verify_platform will check an explicit whitelist and blacklist instead.
The default will now be assumed to be allowed to run anywhere.
For tests that do not specify their platforms explicitly, this has the effect of
enabling these tests on non-linux platforms. For tests that
handle 0" error.
Let's mark it as supported only on systems where the test is working
most of the time (i.e. Linux, FreeBSD and NetBSD).
Reviewed-by: Max Reitz
Signed-off-by: Thomas Huth
---
tests/qemu-iotests/183 | 1 +
1 file changed, 1 insertion(+)
diff --git a/tests/qemu-iotests/183 b/te
041 works fine on Linux, FreeBSD, NetBSD and OpenBSD, but fails on macOS.
Let's mark it as only supported on the systems where we know that it is
working fine.
Reviewed-by: Max Reitz
Signed-off-by: Thomas Huth
---
tests/qemu-iotests/041 | 3 ++-
1 file changed, 2 insertions(+), 1 deletion
in iotest 267 - it has been added to
the "auto" group already, but requires virtio-blk and thus currently
fails with qemu-system-tricore for example. Let's also add aproper
check there.
Reviewed-by: Max Reitz
Signed-off-by: Thomas Huth
---
tests/qemu-iotests/127 | 2 ++
te
for iothreads. For
migration, let's enable 181 and 203 (which also tests iothreads).
(091 would be a good candidate for migration, too, but Alex Bennée
reported that this test fails on ZFS file systems, so it can't be
included yet)
Reviewed-by: Max Reitz
Signed-off-by: Thomas Huth
---
tests/qemu
every
test (which does not sound very appealing), let's rather add a check for
this a central spot in the "check" script instead (so that it is still
possible to run "make check" for qemu-system-tricore for example).
Signed-off-by: Thomas Huth
---
tests/qemu-iotests/check | 12 ++
ew iotests have been added to the QEMU repository
in the past months, so we can now add some new test > 256 instead.
Signed-off-by: Thomas Huth
---
.gitlab-ci.yml | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index d9a90f
On 08/01/2020 14.24, Paolo Bonzini wrote:
> On 08/01/20 14:10, Daniel P. Berrangé wrote:
>> On Wed, Jan 08, 2020 at 01:41:59PM +0100, Paolo Bonzini wrote:
>>> On 08/01/20 11:58, Thomas Huth wrote:
>>>>> "-accel default" could be considered to have vibes
On 19/12/2019 13.19, Kevin Wolf wrote:
> Am 18.12.2019 um 15:43 hat Thomas Huth geschrieben:
>> The python code already contains a possibility to skip tests if the
>> corresponding driver is not available in the qemu binary - use it
>> in more spots to avoid that
On 06/01/2020 14.09, Philippe Mathieu-Daudé wrote:
> Commit 6f6e1698a6 desugarized "-machine accel=" to a list
> of "-accel" options. Since now "-machine accel" and "-accel"
> became incompatible, update the iotests to the new format.
>
> Error reported here:
>
On 07/01/2020 11.14, Paolo Bonzini wrote:
> On 07/01/20 11:03, Thomas Huth wrote:
>>>
>>> vm = QEMUMachine(iotests.qemu_prog)
>>> -vm.add_args('-machine', 'accel=kvm:tcg')
>>> +vm.add_args('-accel', 'kvm', '-accel', 'tcg')
>> Looking at this, I wond
On 07/01/2020 15.37, Paolo Bonzini wrote:
> On 07/01/20 14:55, Christophe de Dinechin wrote:
>> So what about ranking the accelerators, so that all combinaisons
>> -accel=kvm:tcg, -accel=tcg:kvm, -accel kvm -accel tcg, etc would
>
> (I assume you mean "-machine accel=kvm:tcg" and "-machine
On 07/01/2020 15.27, Daniel P. Berrangé wrote:
> On Tue, Jan 07, 2020 at 03:20:40PM +0100, Philippe Mathieu-Daudé wrote:
>> On 1/7/20 3:14 PM, Thomas Huth wrote:
>>> On 07/01/2020 13.54, Daniel P. Berrangé wrote:
>>>> On Tue, Jan 07, 2020 at 01:23:18PM +0100, Paolo Bo
On 23/12/2019 09.39, Paolo Bonzini wrote:
> On 23/12/19 08:43, Vladimir Sementsov-Ogievskiy wrote:
>> diff --git a/vl.c b/vl.c
>> index 86474a55c9..9fb859969c 100644
>> --- a/vl.c
>> +++ b/vl.c
>> @@ -2779,7 +2779,7 @@ static void configure_accelerators(const char
>> *progname)
>> for
501 - 600 of 1251 matches
Mail list logo
