Project

General

Profile

Actions
Copy link

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.

Status:
Resolved
Priority:
Normal
Assignee:
okurz
Category:
Bugs in existing tests
Target version:
SUSE QA - Milestone 18
Start date:
2018-06-08
Due date:
2018-07-31
% Done:

0%

Estimated time:
Difficulty:

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 issues 2 (0 open — 2 closed)

Related to openQA Tests - 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?Resolvedokurz2018-05-132018-06-19

Actions
Related to openQA Tests - action #37000: [opensuse][functional][u][sporadic] test fails in reboot_plasma5 - either stuck in shutdown or not enough waiting time for grub2?Resolvedoorlov2018-06-082018-09-25

Actions
Actions
Copy link
 #1

Updated by okurz almost 6 years ago

  • 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
Actions
Copy link
 #2

Updated by okurz almost 6 years ago

  • 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.

Actions
Copy link
 #3

Updated by okurz almost 6 years ago

  • Target version changed from Milestone 17 to Milestone 17
Actions
Copy link
 #4

Updated by okurz almost 6 years ago

  • Target version changed from Milestone 17 to Milestone 18
Actions
Copy link
 #5

Updated by okurz almost 6 years ago

  • Due date changed from 2018-07-17 to 2018-07-31

It's hackweek time!

Actions
Copy link
 #6

Updated by okurz almost 6 years ago

  • 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".

Actions
Copy link
 #7

Updated by okurz almost 6 years ago

  • Assignee set to okurz
Actions
Copy link
 #8

Updated by okurz almost 6 years ago

  • 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
Actions
Copy link
 #9

Updated by okurz almost 6 years ago

  • Status changed from Workable to Resolved

https://openqa.opensuse.org/tests/713572#next_previous and the last 30 jobs did not fail in the according test modules so my "desktop_runner" changes seem to have helped. The failing scenarios are in most cases handled in #37000

Actions
Copy link

Also available in: Atom PDF