Project

General

Profile

Actions
Copy link

action #27004

closed

[opensuse][sle][functional][yast][y][hard] yast2 gui modules fail to start in the defined time frame

Added by riafarov about 7 years ago. Updated over 5 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
riafarov
Category:
Bugs in existing tests
Target version:
QA - future
Start date:
2017-10-25
Due date:
% Done:

0%

Estimated time:
Difficulty:
hard

Description

In yast2_gui test suite we have random failures most of which appear due to yast module not being able to start.
We have default timeout of 60 seconds, which is not always enough. We also tried to bump all timeouts using TIMEOUT_SCALE variable, which helped, but has not resolved the problem.

Hence, we need to investigate what causes it.

One of the causes is that btrfs balancing in triggered and it significantly affects system performance and this issue can be replicated manually as well. So, we could trigger balancing before running the test suite.
Other idea is to revert to last good snapshot even run was successful, but this will require changes in os-autoinst which may take longer to implement.

Observation

openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-yast2_gui@64bit fails in
yast2_firewall

Reproducible

Fails since (at least) Build 20171023

Expected result

Last good: 20171022 (or more recent)

Acceptance criteria

  • AC1: yast modules start up stable within yast2_gui with no TIMEOUT_SCALE applied
  • AC2: No TIMEOUT_SCALE set on the test suite on neither osd nor o3

Further details

Always latest result in this scenario: latest

Related issues 2 (0 open — 2 closed)

Related to openQA Tests - action #25634: [sle][functional][opensuse][sporadic]test fails in yast2_firewall because "zypper in" times out -> bump timeoutResolvedokurz2017-09-282017-11-08

Actions
Related to openQA Tests - action #26104: test fails in yast2_langResolvedriafarov2017-10-17

Actions
Actions
Copy link

Also available in: Atom PDF