Project

General

Profile

action #41348

[qam][sle] test fails in user_settings - name/password typed into incorrect fields

Added by bfilho about 3 years ago. Updated over 2 years ago.

Status:
Resolved
Priority:
High
Assignee:
Category:
Bugs in existing tests
Target version:
-
Start date:
2018-09-19
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Observation

openQA test in scenario sle-12-SP3-Server-DVD-Updates-x86_64-qam-allpatterns+addons@64bit fails in
user_settings

Reproducible

Fails since (at least) Build 20180916-1

Expected result

Last good: 20180915-2 (or more recent)

Further details

Always latest result in this scenario: latest

It seems that the script is missing filling user information. Coolo noticed some error information on https://openqa.suse.de/tests/2061883#step/user_settings/55 and similar on other runs.
I believe its something around the following lines:
...
wait_screen_change { type_string $realname };
send_key 'tab'; # Select password field
send_key 'tab';
$self->type_password_and_verification;
...

History

#1 Updated by msmeissn about 3 years ago

Should we somehow wait for the full realname to appear via a needle match?

this would avoid this typing race condition perhaps?

#2 Updated by pcervinka about 3 years ago

  • Subject changed from test fails in user_settings to [qam][sle]test fails in user_settings - name/password typed into incorrect fields
  • Assignee set to okurz

Oliver could you please check? (as you are maintainer).
It seems that

    wait_screen_change { type_string $realname };
    send_key 'tab';      # Select password field
    send_key 'tab';
    $self->type_password_and_verification;

Thank you.

#3 Updated by msmeissn about 3 years ago

ping... this is a flaky test that regulary fails for us , it would help to have it more stable

#4 Updated by okurz about 3 years ago

  • Subject changed from [qam][sle]test fails in user_settings - name/password typed into incorrect fields to [qam][sle] test fails in user_settings - name/password typed into incorrect fields
  • Priority changed from Normal to High

I doubt that the test module does anything wrong here. I am not aware of any problem within "user_settings" within SLE validation tests for multiple months and in the described scenario it is very likely to happen. https://openqa.suse.de/tests/2114659#step/user_settings/4 shows characters missing when typing the username. So there is not much different we can do in the test except for typing slower but why should we?

Looking at the history in more details it seems that the tests were looking better at https://openqa.suse.de/tests/2033951#next_previous from 22 days I can not find user_settings failing in 25 tests.

I suspect it can only be one problem: The questionable approach of adding the huge amount of addon repositories over the GUI which is very far from what a sane human would do is making the yast installer hit which might be supported by the observation within https://openqa.suse.de/tests/2110537/file/user_settings-ps_auxf with a huge list of defunct zombie processes. I guess I can not help much there. We could try to type super slow or wait until the installer recovers from whatever it is busy with for the time being if that will help at all but this also feels so wrong. So WDYT?

#6 Updated by okurz about 3 years ago

https://bugzilla.suse.com/show_bug.cgi?id=1110485 created for the 4800 tar zombies.

#7 Updated by okurz about 3 years ago

  • Status changed from New to Blocked

Sorry, don't know what to do better. I guess we should work on #41921 first?

#8 Updated by osukup about 3 years ago

okurz wrote:

Sorry, don't know what to do better. I guess we should work on #41921 first?

yes, proper solution of #41921 with autoyast can workaround this problem :D

#9 Updated by okurz over 2 years ago

  • Status changed from Blocked to Resolved

Main maintenance tests have been converted to being based on autoyast. The scenario as in https://openqa.suse.de/tests/latest?distri=sle&test=qam-allpatterns%2Baddons&flavor=Server-DVD-Updates&arch=x86_64&version=12-SP3&machine=64bit#next_previous and jobs in its history show that it is really stable now.

Also available in: Atom PDF