action #37003
closed
[opensuse][functional][u][sporadic] test fails in network_configuration - xterm does not start
Added by mloviska almost 6 years ago.
Updated almost 6 years ago.
Category:
Bugs in existing tests
Target version:
SUSE QA - Milestone 18
Description
Observation¶
openQA test in scenario opensuse-Tumbleweed-NET-x86_64-update_13.2@64bit fails in
network_configuration
Reproducible¶
Fails since (at least) Build 20180606 (current job)
Expected result¶
Last good: 20180605 (or more recent)
Further details¶
Always latest result in this scenario: latest
- Related to action #36117: [functional][u][sporadic] test fails in xterm to show "xterm" (needle tag desktop-runner-plasma-suggestions) in krunner - system slower just after login? added
- Subject changed from [opensuse][functional][u] test fails in network_configuration - xterm does not start to [opensuse][functional][u][sporadic] test fails in network_configuration - xterm does not start
- Due date set to 2018-07-17
- Target version set to Milestone 17
This is closely related to #36117 . In #36117 we made sure that "x11/desktop_runner" is the first module to be scheduled immediately after login. Here the special module called immediately after "first_boot" is "fixup/network_configuration" which of course can fail to show the desktop runner suggestions in time. We should prevent calling any other x11 module before x11/desktop_runner. We could try to simply schedule "x11/desktop_runner" additionally before "fixup/network_configuration". The alternative would be to implement the "fixup/network_configuration" differently by making it a console test and not relying on the X11 responsiveness in this system state.
- Target version changed from Milestone 17 to Milestone 17
- Target version changed from Milestone 17 to Milestone 18
- Due date changed from 2018-07-17 to 2018-07-31
- Status changed from New to Workable
Worth to check this scenario with statistical investigation after my last changes, e.g. after introducing the specific test module "desktop_runner".
- Related to action #37000: [opensuse][functional][u][sporadic] test fails in reboot_plasma5 - either stuck in shutdown or not enough waiting time for grub2? added
- Status changed from Workable to Resolved
Also available in: Atom
PDF