action #33571
closed
[opensuse][functional][u][medium] test fails in shutdown - emoticon settings are opened
Added by jorauch about 6 years ago.
Updated over 5 years ago.
Category:
Bugs in existing tests
Description
Observation¶
openQA test in scenario opensuse-15.0-NET-x86_64-update_Leap_42.2_kde@64bit fails in
shutdown
The emoticon settings are opened not only in this case, also observed this in vlc tests.
Tasks:
- find out whats going on here
- stop that behaviour
Reproducible¶
Fails since (at least) Build 148.1
Expected result¶
Last good: 147.1 (or more recent)
Further details¶
Always latest result in this scenario: latest
- Related to action #31687: [opensuse][functional][medium][u] x11_start_program does not care if program can not be called in desktop runner even after three 'ret' presses with "valid" and "target_match" added
- Subject changed from [opensuse][functional][medium][research] test fails in shutdown - emoticon settings are opened to [opensuse][functional][u][medium] test fails in shutdown - emoticon settings are opened
- Target version set to Milestone 16
I don't know what you mean with the [research] label but for me this task is a standard "we need to understand what's going on and fix it" ticket. The research ones are more for "research what possibilities we have and present that to the team"
- Due date set to 2018-05-22
- Target version deleted (
Milestone 16)
- Target version set to Milestone 16
I think this is caused by pressing enter too early when only e is pressed and therefore the emoticons settings are selected
If this is correct we should fix it in x11_start_program
- Related to action #30805: [functional][opensuse][leap][medium][u] first test after reboot fails in krunner, potential system overload (was: test fails in inkscape - typing too fast?) added
- Related to coordination #35215: [functional][u][epic][medium] test fails on shutdown module added
- Status changed from Workable to Blocked
- Assignee set to okurz
I assume we are blocked here by #35215
- Due date changed from 2018-05-22 to 2018-06-05
- Status changed from Blocked to Workable
okurz wrote:
I assume we are blocked here by #35215
blocker is resolved - unblocking and moving to next sprint
- Status changed from Workable to In Progress
- Status changed from In Progress to Resolved
Also available in: Atom
PDF