action #27004
Updated by okurz about 6 years ago
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](http://openqa.opensuse.org/tests/513279/modules/yast2_firewall/steps/5)
## Reproducible
Fails since (at least) Build [20171023](http://openqa.opensuse.org/tests/512985)
## Expected result
Last good: [20171022](http://openqa.opensuse.org/tests/512100) (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](http://openqa.opensuse.org/tests/latest?flavor=DVD&arch=x86_64&version=Tumbleweed&machine=64bit&test=yast2_gui&distri=opensuse)