QA (public) » openQA Project (public) » openQA Tests (public)

filed bsc#1075038 for bootloader.
this issue blocks further tests.

the latest test run from yast2_ncurses doesn't show this issue: https://openqa.suse.de/tests/latest?version=15&machine=64bit&test=yast2_ncurses&distri=sle&flavor=Installer-DVD&arch=x86_64#step/consoletest_finish/12

for me there is no issue with consoletest_finish, however I will run a couple tests to be sure that is really no issue for now.

What I can see from the logs:

2018-01-11T10:41:31.0076 CET] [debug] >>> testapi::_handle_found_needle: found displaymanager-20171123, similarity 1.00 @ 339/266
[2018-01-11T10:41:31.0076 CET] [debug] /var/lib/openqa/cache/tests/sle/tests/console/consoletest_finish.pm:44 called utils::ensure_unlocked_desktop
[2018-01-11T10:41:31.0076 CET] [debug] <<< testapi::send_key(key='ret', do_wait=0)
[2018-01-11T10:41:31.0282 CET] [debug] /var/lib/openqa/cache/tests/sle/tests/console/consoletest_finish.pm:44 called utils::ensure_unlocked_desktop
[2018-01-11T10:41:31.0282 CET] [debug] <<< testapi::wait_still_screen(similarity_level=47, stilltime=2, timeout=30)
[2018-01-11T10:41:33.0299 CET] [debug] >>> testapi::wait_still_screen: detected same image for 2 seconds
[2018-01-11T10:41:33.0391 CET] [debug] # Test died: ensure_unlocked_desktop repeated too much. Check for X-server crash. at /var/lib/openqa/cache/tests/sle/lib/utils.pm line 373.

--
displaymanager-20171123 found and matched, but I see displaymanager-20180111 is available and has 98% match.

Why?

debugging ensure_unlocked_desktop in utils.pm:

sub ensure_unlocked_desktop {
my $counter = 10;
while ($counter--) {
assert_screen [qw(displaymanager displaymanager-password-prompt generic-desktop screenlock gnome-screenlock-password)], no_wait => 1;
if (match_has_tag 'displaymanager') {
if (check_var('DESKTOP', 'minimalx')) {
type_string "$username";
save_screenshot;
}
send_key 'ret';
diag "______________ username $username typed?";
}
if ((match_has_tag 'displaymanager-password-prompt') || (match_has_tag 'gnome-screenlock-password')) {
if ($password ne '') {
type_password;
assert_screen [qw(locked_screen-typed_password login_screen-typed_password)];
}
send_key 'ret';
diag "____________ password $password input?";
}

http://e13.suse.de/tests/248#step/consoletest_finish/11

shows that it is working, the question it doesn't screenlock at more, ensure_unlocked_desktop just works...

try with following changes:

if (match_has_tag 'displaymanager') {
if (check_var('DESKTOP', 'minimalx')) {
if ($username ne '') {
type_string "$username";
}
save_screenshot;
}
send_key 'ret';
}

I doubt that username has not been handled properly. type_string $username seems not to work...

scc registation is not working at moment :(

https://bugzilla.suse.com/show_bug.cgi?id=1075723

This blocks my testing...

The build before did not show this bug but showed the unlock problem as well. I don't see how that would block. Anyway, the new build has SCC registration working fine again, problem reproduced, most recent example: https://openqa.suse.de/tests/1385494#step/consoletest_finish/13

scc issue got resolved, so continue working on this ticket.

http://e13.suse.de/tests/253#
yast2_bootloader blocks the test.

As discussed with zluo the needle displaymanager-20171123 looks invaild. Proposed to delete it and then see what's going on.

http://e13.suse.de/tests/257#step/consoletest_finish/16

delete needle displaymanager-20171123 and fixed locked_screen-typed_password, it looks good now.

Needle PR:

https://gitlab.suse.de/openqa/os-autoinst-needles-sles/merge_requests/645

It is needle displaymanager-20180112 which caused this failure in my tests:
https://openqa.suse.de/tests/1385510#step/consoletest_finish%231/13

I will submit a needle MR to remove displaymanager-20180112
https://gitlab.suse.de/openqa/os-autoinst-needles-sles/merge_requests/646

qkzhu@suse.com created displaymanager needle again and breaks the test...