diff options
| author | Max Reitz <mreitz@redhat.com> | 2019-08-15 17:36:37 +0200 |
|---|---|---|
| committer | Max Reitz <mreitz@redhat.com> | 2019-09-03 14:55:35 +0200 |
| commit | c64c3ae35b84b41140f6cd888624bea13ce4fc7e (patch) | |
| tree | 633f4508bd9aafa8e3c73b6366c2f8abf67e3cf0 /tests/qemu-iotests/110 | |
| parent | 325dd915b231801e48f89b38a4bfb89c8956098c (diff) | |
| download | qemu-c64c3ae35b84b41140f6cd888624bea13ce4fc7e.zip qemu-c64c3ae35b84b41140f6cd888624bea13ce4fc7e.tar.gz qemu-c64c3ae35b84b41140f6cd888624bea13ce4fc7e.tar.bz2 | |
iotests: Disable 110 for vmdk.twoGbMaxExtentSparse
The error message for the test case where we have a quorum node for
which no directory name can be generated is different: For
twoGbMaxExtentSparse, it complains that it cannot open the extent file.
For other (sub)formats, it just notes that it cannot determine the
backing file path. Both are fine, but just disable twoGbMaxExtentSparse
for simplicity's sake.
Signed-off-by: Max Reitz <mreitz@redhat.com>
Reviewed-by: John Snow <jsnow@redhat.com>
Message-id: 20190815153638.4600-7-mreitz@redhat.com
Reviewed-by: John Snow <jsnow@redhat.com>
Signed-off-by: Max Reitz <mreitz@redhat.com>
Diffstat (limited to 'tests/qemu-iotests/110')
| -rwxr-xr-x | tests/qemu-iotests/110 | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/tests/qemu-iotests/110 b/tests/qemu-iotests/110 index 2cdc7c8..2ef516b 100755 --- a/tests/qemu-iotests/110 +++ b/tests/qemu-iotests/110 @@ -40,7 +40,8 @@ trap "_cleanup; exit \$status" 0 1 2 3 15 # Any format supporting backing files _supported_fmt qed qcow qcow2 vmdk _supported_proto file -_unsupported_imgopts "subformat=monolithicFlat" "subformat=twoGbMaxExtentFlat" +_unsupported_imgopts "subformat=monolithicFlat" "subformat=twoGbMaxExtentFlat" \ + "subformat=twoGbMaxExtentSparse" TEST_IMG_REL=$(basename "$TEST_IMG") |