Actions
action #31027
closed[functional][opensuse][leap][yast] test fails in yast2_control_center - too fast to type ctrl-o?
Status:
Resolved
Priority:
High
Assignee:
Category:
Bugs in existing tests
Target version:
Start date:
2018-01-29
Due date:
2018-03-13
% Done:
0%
Estimated time:
Difficulty:
Description
Observation¶
openQA test in scenario opensuse-15.0-DVD-x86_64-yast2_gui@64bit fails in
yast2_control_center
Looking at the video, the test seems to be too fast to type ctrl-o. The yast module is not ready yet. In the previously, cloned job the test failed in another yast module, likely in a similar way.
Reproducible¶
Fails since (at least) Build 54.1
Expected result¶
Last good: https://openqa.opensuse.org/tests/617961
Further details¶
Always latest result in this scenario: latest
Updated by okurz almost 7 years ago
- Subject changed from test fails in yast2_control_center to [opensuse][leap]test fails in yast2_control_center - too fast to type ctrl-o?
- Due date set to 2018-03-13
- Target version set to Milestone 14
Updated by okurz almost 7 years ago
- Related to action #25878: [sle][functional][y][sle15][easy][bsc#1062331] create soft-failure for yast2_control-center added
Updated by okurz almost 7 years ago
- Related to action #31138: [tools][opensuse]test fails in yast2_control_center - loosing keys? added
Updated by okurz almost 7 years ago
- Subject changed from [opensuse][leap]test fails in yast2_control_center - too fast to type ctrl-o? to [functional][opensuse][leap]test fails in yast2_control_center - too fast to type ctrl-o?
Updated by riafarov almost 7 years ago
- Subject changed from [functional][opensuse][leap]test fails in yast2_control_center - too fast to type ctrl-o? to [functional][opensuse][leap][yast] test fails in yast2_control_center - too fast to type ctrl-o?
- Description updated (diff)
- Status changed from New to In Progress
Updated by riafarov almost 7 years ago
- Status changed from In Progress to Resolved
Works here https://openqa.opensuse.org/tests/619605#step/yast2_control_center/19 issue mentioned in the ticket was due to missing needle, and then we got screensaver, so needle didn't match in 180 seconds.
Actions