action #26104
closed
Added by dimstar over 6 years ago.
Updated over 6 years ago.
Category:
Bugs in existing tests
Description
Observation¶
openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-yast2_gui@64bit fails in
yast2_lang
Reproducible¶
Fails since (at least) Build 20171006
Expected result¶
Last good: 20171005 (or more recent)
Further details¶
Always latest result in this scenario: latest
More info¶
It seemd the machine 'stalled' somehow completely. yast2 does not start, the collection of debug logs fails at the point it calls 'rpmverify' and all future commands simply are ignored
- Status changed from New to In Progress
Machine is not really stalled, we can even see that time is updated. Increasing timeout to 180 for module to start seems to help. I've added TIMEOUT_SCALE variable to the test suite on o3 to see if it helps. I could reproduce the issue in 5 out of 6 runs locally. With increased timeout in 5 runs test module haven't failed even once. Investigating if anything else can be improved.
One of our hypothesis is that if btrfs balance is triggered, SUT has significant performance degradation. I was able to replicate issue when set RAM to 512 on VM, started balancing btrfs and then tried to run yast module. SUT becomes very slow and it took up to few minutes to start yast control center. Before balancing was triggered, gui shows up immediately. In the serial output we see that for the failed runs balancing is triggered.
- Status changed from In Progress to Feedback
- Status changed from Feedback to Resolved
- Related to action #25634: [sle][functional][opensuse][sporadic]test fails in yast2_firewall because "zypper in" times out -> bump timeout added
- Related to action #27004: [opensuse][sle][functional][yast][y][hard] yast2 gui modules fail to start in the defined time frame added
Also available in: Atom
PDF