action #16604
closed[sle][functional][desktop]test fails in sshxterm - delays on typing commands in terminal
0%
Description
Updated by asmorodskyi about 7 years ago
reproduces for Server functional tests - https://openqa.suse.de/tests/767907#step/sshxterm/4
Updated by dgutu about 7 years ago
Still an issue - https://openqa.suse.de/tests/770042
Updated by dgutu about 7 years ago
Another example - https://openqa.suse.de/tests/768820#step/ssh_cleanup/1
Updated by dgutu about 7 years ago
Another one - https://openqa.suse.de/tests/768802
Updated by dgutu about 7 years ago
- Subject changed from test fails in sshxterm to test fails in sshxterm - delays on typing commands in terminal
A lot of tests are failing because suddenly the chars in the console are starting to be typed with some delay.
Updated by okurz about 7 years ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: USBinstall@uefi
http://openqa.suse.de/tests/790200
Updated by okurz about 7 years ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: USBinstall@uefi
http://openqa.suse.de/tests/790200
Updated by okurz over 6 years ago
- Subject changed from test fails in sshxterm - delays on typing commands in terminal to [sle][functional][desktop]test fails in sshxterm - delays on typing commands in terminal
- Target version set to Milestone 11
Updated by okurz over 6 years ago
- Related to action #26852: [sle][functional][tools][BLOCKED][bsc#1041747] assert_script_run sometimes/randomly type a duplicate letter in the beginning added
Updated by okurz over 6 years ago
- Status changed from New to Resolved
- Assignee set to okurz
I assume commit 2e98c8c2
Author: Oliver Kurz okurz@suse.de
Date: Fri Oct 6 20:05:18 2017 +0200
Check target match with x11_start_program by default in all instances
As checking for a screen with "assert_screen" after "x11_start_program" is the
standard action and it allows to save time because there is a target to look
for this is now the default action saving quite some time for all X11 tests.
Exceptions can still be applied, for example by specifying "valid => 0" on the
call of "x11_start_program".
Validation runs:
* SLE 12 SP1 qam-gnome: http://lord.arch/tests/7609 glxgears failed
because of differing no_wait, update after newest test
* openSUSE TW yast2_gui: http://lord.arch/tests/7608
should cover this