action #63139
closed[opensuse][functional][y] test fails in yast2_control_center and yast2_firewall due to Screenlock/screensaver shown
0%
Description
Observation¶
openQA test in scenario opensuse-15.2-DVD-aarch64-yast2_gui@aarch64 fails in
yast2_control_center
In current Leap 15.2 (due to new GNOME?), Screenlock/screensaver shown when tty is switched from a console tty to a graphic tty. It is no a matter of time.
yast2_control_center and yast2_firewall are affected.
Test suite description¶
Maintainer: qsf-y
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.
Temporarily added YAST2_GUI_TERMINATE_PREVIOUS_INSTANCES to see if helps. This variable triggers code which terminates all yast2 processes before starting new one. (see poo#26104).
Reproducible¶
Fails since (at least) Build 78.1
Expected result¶
Last good: 77.4 (or more recent)
Further details¶
Always latest result in this scenario: latest
Suggestions¶
Updated by zluo about 4 years ago
- Subject changed from test fails in yast2_control_center and yast2_firewall due to Screenlock/screensaver shown to [opensuse][functional][y] test fails in yast2_control_center and yast2_firewall due to Screenlock/screensaver shown
Updated by okurz about 4 years ago
@lkocman just trying to explain and come to a mutual understanding of expectations: The ticket was added 13 days ago and on the same day subsequently triaged as fitting for QSF-y with the tags "[functional][y]". The status is "New", the priority is "Normal". QSF-y works with 2 week sprints. Tickets which are not handled in a priority lane are planned with the "Due date" field which has not been assigned for this ticket. So based on that and my previous experience the ETA is around weeks/months.
Updated by riafarov about 4 years ago
- Due date set to 2020-03-10
- Target version set to Milestone 33
Updated by riafarov about 4 years ago
@okurz thanks for your explanation!
@lkocman: I will also add one more point, TW for us is of a great interest because is upstream of SLES. Arm port is not of same value, unfortunately and we are quite busy with SLES now.
So in case you want to improve our processes, we can have a discussion of a bigger scope.
Updated by JERiveraMoya about 4 years ago
- Status changed from New to Workable
- Estimated time set to 3.00 h
Updated by oorlov about 4 years ago
- Status changed from Workable to In Progress
- Assignee set to oorlov
Updated by ggardet_arm about 4 years ago
This seems to be fixed. Probably related to https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/9661
Updated by oorlov about 4 years ago
- Status changed from In Progress to Rejected
Thank you ggardet_arm, I've executed the run to confirm that it works: https://openqa.opensuse.org/tests/1190365
Closed.