action #153169
closed
coordination #151816: [epic] Handle openQA fixes and job group setup
[sporadic] YaST module is not being closed in yast2_security
Added by JRivrain 5 months ago.
Updated 4 months ago.
Description
Observation¶
That same test passed earlier with the same build. So something probably changed in the test environment.
We need to figure out what.
openQA test in scenario sle-15-SP6-Online-x86_64-yast2_gui@64bit fails in
yast2_security
Test suite description¶
Maintainer: zluo, riafarov
Test for yast2 UI, GUI only. Running on created gnome images which provides both text console for ncurses UI tests as well as the gnome environment for the GUI tests.
Reproducible¶
Fails since (at least) Build 45.1 (current job)
Expected result¶
Last good: 45.1 (or more recent)
Further details¶
Always latest result in this scenario: latest
- Description updated (diff)
- Subject changed from Yast app is not being closed in yast2_security to Yast module is not being closed in yast2_security
- Tags set to qe-yam-jan-sprint
- Subject changed from Yast module is not being closed in yast2_security to [sporadic] YaST module is not being closed in yast2_security
- Status changed from New to Workable
- Priority changed from Normal to Low
- Parent task set to #151816
- Status changed from Workable to In Progress
- Assignee set to JRivrain
That was no a sporadic issue, it happened each time. Looks like it was fixed, let's see.
- Subject changed from [sporadic] YaST module is not being closed in yast2_security to YaST module is not being closed in yast2_security
- Subject changed from YaST module is not being closed in yast2_security to [sporadic] YaST module is not being closed in yast2_security
- Status changed from In Progress to Resolved
The problem was fixed, hopefully will not appear again.
Also available in: Atom
PDF