action #36150
closed[opensuse][functional][u][sporadic] test fails in shutdown on unsafe code looking for "sddm_shutdown_option_btn"
0%
Description
Observation¶
openQA test in scenario opensuse-5.12.80-Krypton-Live-x86_64-krypton-live@64bit-2G fails in
shutdown
Reproducible¶
Looking at https://openqa.opensuse.org/tests/675741?limit_previous=100#previous we can see this scenario failing 2/100 in shutdown with the same symptoms.
Acceptance criteria¶
- AC1: test module "shutdown" runs stable
- AC2: Test code uses no check_screen or only with 0 second timeout
Further details¶
Always latest result in this scenario: latest
Updated by oorlov over 6 years ago
opensuse-Tumbleweed-KDE-Live-x86_64-Build20180520-kde-live-wayland@64bit_virtio-2G failed with the same symptoms.
Updated by okurz over 6 years ago
- Related to coordination #35215: [functional][u][epic][medium] test fails on shutdown module added
Updated by okurz over 6 years ago
- Related to action #36279: [sle][functional][u][s390x][medium] test fails in reboot_gnome on bsc#1085181 - help with investigation using new shutdown debug method added
Updated by okurz over 6 years ago
- Target version changed from Milestone 17 to Milestone 17
Updated by riafarov over 6 years ago
Check if already resolved first as oorlov has fixed couple of issues with shutdown.
Updated by oorlov over 6 years ago
I guess it is happening due to our workaround in 'utils->poweroff_x11()' subroutine:
assert_and_click 'sddm_shutdown_option_btn';
if (check_screen([qw(sddm_shutdown_option_btn sddm_shutdown_btn)], 3)) {
# sometimes not reliable, since if clicked the background
# color of button should changed, thus check and click again
if (match_has_tag('sddm_shutdown_option_btn')) {
assert_and_click 'sddm_shutdown_option_btn';
}
Shutdown button is clicked in assert_and_click 'sddm_shutdown_option_btn'
, then the test checks for the same button again. It is still shown, then it tries to click it again, but it is already disappear.
So, the next step for the ticket is to understand why that workaround was added, and then improve it with intelligent check or even remove that workaround at all.
Updated by riafarov over 6 years ago
- Related to deleted (coordination #35215: [functional][u][epic][medium] test fails on shutdown module)
Updated by riafarov over 6 years ago
- Blocked by coordination #35215: [functional][u][epic][medium] test fails on shutdown module added
Updated by mgriessmeier over 6 years ago
- Due date changed from 2018-07-03 to 2018-07-17
Updated by okurz over 6 years ago
- Due date changed from 2018-07-17 to 2018-07-31
Updated by okurz over 6 years ago
- Status changed from Blocked to In Progress
- Assignee set to okurz
Updated by okurz over 6 years ago
- Blocked by deleted (coordination #35215: [functional][u][epic][medium] test fails on shutdown module)
Updated by okurz over 6 years ago
- Related to coordination #35215: [functional][u][epic][medium] test fails on shutdown module added
Updated by okurz over 6 years ago
- Status changed from In Progress to Resolved
- Target version changed from Milestone 17 to Milestone 18
Updated by oorlov over 6 years ago
- Has duplicate action #36040: [opensuse][functional][u] test fails in shutdown - need a way to check after shutdown needle got matched but shutdown hasn't been executed for unknown reason added
Updated by oorlov over 6 years ago
- Has duplicate deleted (action #36040: [opensuse][functional][u] test fails in shutdown - need a way to check after shutdown needle got matched but shutdown hasn't been executed for unknown reason)