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 <awilliam@redhat.com>
This commit is contained in:
Adam Williamson 2020-01-15 15:13:44 +00:00
parent 1e025c0b27
commit e9fa0b4bde
2 changed files with 2 additions and 2 deletions

View File

@ -14,7 +14,7 @@ sub run {
menu_launch_type('boxes'); menu_launch_type('boxes');
assert_and_click('boxes_new_connection'); assert_and_click('boxes_new_connection');
assert_and_click('boxes_remote'); 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_allow_inhibit');
assert_and_click('boxes_fullscreen'); assert_and_click('boxes_fullscreen');
} }

View File

@ -16,7 +16,7 @@ sub run {
desktop_vt; desktop_vt;
menu_launch_type 'terminal'; menu_launch_type 'terminal';
wait_still_screen 5; wait_still_screen 5;
type_safely "vncviewer -FullScreen -listen\n"; type_very_safely "vncviewer -FullScreen -listen\n";
mutex_create 'vncconnect_client_ready'; mutex_create 'vncconnect_client_ready';
} }