Actions
action #58259
closed[qam] test fails in yast2_storage_ng, new behavior
Start date:
2019-10-21
Due date:
2019-10-23
% Done:
100%
Estimated time:
1.00 h
Difficulty:
Description
Observation¶
openQA test in scenario sle-15-SP1-Server-DVD-Updates-x86_64-mau-extratests-yast2ui@64bit fails in
yast2_storage_ng
Test suite description¶
Run YaST2 GUI tests
Reproducible¶
Fails since (at least) Build 20191015-2
Expected result¶
Last good: 20191015-1 (or more recent)
Further details¶
Always latest result in this scenario: latest
Updated by pstivanin over 4 years ago
- Status changed from New to In Progress
- Assignee set to pstivanin
Updated by coolo over 4 years ago
Shall we take this out for now or is there a fix on the horizon?
Updated by pstivanin over 4 years ago
- Due date set to 2019-10-25
- Start date changed from 2019-10-16 to 2019-10-21
I'll start working on it later today!
Updated by pstivanin over 4 years ago
- Due date changed from 2019-10-25 to 2019-10-23
- % Done changed from 0 to 100
- Estimated time set to 1.00 h
That was actually not a new behavior but a sporadic bug. The key was sent before the window appeared, that's why it failed (busy worker? slow network?)
I couldn't reproduce it, but the fix I made should prevent that.
https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/8754/files
Updated by pstivanin over 4 years ago
- Status changed from In Progress to Resolved
Actions