From e9fa0b4bdec16e8daa41b5fc66129e2466eae213 Mon Sep 17 00:00:00 2001 From: Adam Williamson Date: Wed, 15 Jan 2020 15:13:44 +0000 Subject: [PATCH] Change type_safely in VNC tests to type_very_safely We seem to have problems with the typing here on ppc64le, so let's make it safer. Signed-off-by: Adam Williamson --- tests/_vnc_client_connect.pm | 2 +- tests/_vncconnect_client_setup.pm | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/tests/_vnc_client_connect.pm b/tests/_vnc_client_connect.pm index 60e8e901..e1bf6091 100644 --- a/tests/_vnc_client_connect.pm +++ b/tests/_vnc_client_connect.pm @@ -14,7 +14,7 @@ sub run { menu_launch_type('boxes'); assert_and_click('boxes_new_connection'); assert_and_click('boxes_remote'); - type_safely("vnc://10.0.2.114:5901\n"); + type_very_safely("vnc://10.0.2.114:5901\n"); assert_and_click('boxes_allow_inhibit'); assert_and_click('boxes_fullscreen'); } diff --git a/tests/_vncconnect_client_setup.pm b/tests/_vncconnect_client_setup.pm index 018acf8c..c9c8e582 100644 --- a/tests/_vncconnect_client_setup.pm +++ b/tests/_vncconnect_client_setup.pm @@ -16,7 +16,7 @@ sub run { desktop_vt; menu_launch_type 'terminal'; wait_still_screen 5; - type_safely "vncviewer -FullScreen -listen\n"; + type_very_safely "vncviewer -FullScreen -listen\n"; mutex_create 'vncconnect_client_ready'; }