action #76867
closed'Next' key didn't reach SUT in yast2_rmt
0%
Description
Observation¶
openQA test in scenario sle-15-SP3-Online-s390x-yast2_ncurses_gnome@s390x-kvm-sle12 fails in
yast2_rmt
For this module I could see multiple actions that are running on the background and logged, so we need better synchronization mechanism to not miss this key at the end of the configuration.
Test suite description¶
Test for yast2 UI, ncurses only.
Test suite requires HDD settings to be set, we use inheritance for that.
Reproducible¶
Fails since (at least) Build 63.1
Expected result¶
Last good: 59.1 (or more recent)
Further details¶
Always latest result in this scenario: latest
Updated by riafarov over 3 years ago
- Priority changed from Normal to High
- Target version set to SLE 15 SP3
Updated by riafarov over 3 years ago
- Status changed from New to Workable
- Priority changed from High to Normal
Updated by JERiveraMoya over 3 years ago
- Status changed from Workable to Rejected
This error is not seen anymore, neither in our group: https://openqa.suse.de/tests/4951107
nor trying a loop of runs: https://openqa.suse.de/tests/overview?distri=sle&version=15-SP3&build=jknphy%2Fos-autoinst-distri-opensuse%23fix_yast2_rmt