Actions
action #36117
closed[functional][u][sporadic] test fails in xterm to show "xterm" (needle tag desktop-runner-plasma-suggestions) in krunner - system slower just after login?
Status:
Resolved
Priority:
Normal
Assignee:
Category:
Bugs in existing tests
Target version:
SUSE QA (private) - Milestone 17
Start date:
2018-05-13
Due date:
2018-06-19
% Done:
0%
Estimated time:
Difficulty:
Description
Observation¶
openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-update_13.2@64bit fails in
xterm
to show the "xterm" suggestion in krunner (in time). The test module "xterm" is scheduled just after "user_gui_login" so we try to open krunner shortly after logging in where the system naturally is still more busy than in a later step when we the session is idle. This might be a problem even more in the case of upgrades, maybe because some older data is automatically migrated in user services, e.g. in plasma.
Reproducible¶
Fails sporadically, e.g. 8 jobs ago in the same scenario: https://openqa.opensuse.org/tests/668678#step/xterm/4
Expected result¶
Upgrade tests pass the krunner step in plasma x11 tests in a stable way
Suggestions¶
- Find a smaller reproducer, e.g. load from snapshot before GUI session login, load xterm after that
- Just wait longer in general in desktop-runner, especially when it is krunner
- Alternative: Make sure to wait longer after the login, e.g. in user_gui_login, open krunner (or generic desktop-runner), wait for it show the suggestion and exit without executing the command (without 'ret' press) -> Con: Potentially complicated logic to repeat what other tests do anyway with
x11_start_program
- Alternative: Just wait longer in xterm because it most likely is the first test module after login -> Con: Makes modules more dependant on order
Further details¶
Always latest result in this scenario: latest
Actions