summaryrefslogtreecommitdiffstats
path: root/tests/qemu-iotests/028
diff options
context:
space:
mode:
authorAndrey Shinkevich2019-09-04 11:11:23 +0200
committerKevin Wolf2019-09-13 12:18:37 +0200
commitfbd1c378385f5405f9d6178e4662bf8744653e8d (patch)
tree2995da0914ba906c3fde520785d75fed831daa28 /tests/qemu-iotests/028
parentiotests: Valgrind fails with nonexistent directory (diff)
downloadqemu-fbd1c378385f5405f9d6178e4662bf8744653e8d.tar.gz
qemu-fbd1c378385f5405f9d6178e4662bf8744653e8d.tar.xz
qemu-fbd1c378385f5405f9d6178e4662bf8744653e8d.zip
iotests: extended timeout under Valgrind
As the iotests run longer under the Valgrind, the QEMU_COMM_TIMEOUT is to be increased in the test cases 028, 183 and 192 when running under the Valgrind. Suggested-by: Roman Kagan <rkagan@virtuozzo.com> Signed-off-by: Andrey Shinkevich <andrey.shinkevich@virtuozzo.com> Reviewed-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com> Reviewed-by: John Snow <jsnow@redhat.com> Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Diffstat (limited to 'tests/qemu-iotests/028')
-rwxr-xr-xtests/qemu-iotests/0286
1 files changed, 5 insertions, 1 deletions
diff --git a/tests/qemu-iotests/028 b/tests/qemu-iotests/028
index 01f495912f..71301ec6e5 100755
--- a/tests/qemu-iotests/028
+++ b/tests/qemu-iotests/028
@@ -110,7 +110,11 @@ echo
qemu_comm_method="monitor"
_launch_qemu -drive file="${TEST_IMG}",cache=${CACHEMODE},id=disk
h=$QEMU_HANDLE
-QEMU_COMM_TIMEOUT=1
+if [ "${VALGRIND_QEMU}" == "y" ]; then
+ QEMU_COMM_TIMEOUT=7
+else
+ QEMU_COMM_TIMEOUT=1
+fi
# Silence output since it contains the disk image path and QEMU's readline
# character echoing makes it very hard to filter the output. Plus, there