action #29259
closed[opensuse][krypton][wayland][x11regressions][hard] test fails in kontact - Wrong synchronization between commands - next command was type too early
0%
Description
Observation¶
From command "kontakt" we can only see the n.
openQA test in scenario opensuse-5.11.90-Krypton-Live-x86_64-krypton-live-wayland@64bit_virtio-2G fails in
kontact
H1: load related problem
H2: ACCEPTED wayland bug -> 6/6 failed
Reproducible¶
Fails since (at least) Build 1.1
Expected result¶
Last good: (unknown) (or more recent)
Further details¶
Always latest result in this scenario: latest
Updated by okurz over 6 years ago
the latest build seems to type "kontact" correctly but it does not start. Might be related to the performance of the live-CD
Updated by nicksinger over 6 years ago
- Status changed from New to In Progress
While the HMC loads all the time I try to reproduce the issue (http://openqa.glados.qa.suse.de/tests/3). I can confirm @okurz' observation that it types everything but kontact does not start.
Updated by okurz over 6 years ago
- Due date set to 2018-01-16
- Target version set to Milestone 13
Updated by okurz over 6 years ago
- Subject changed from test fails in kontact - Wrong synchronization between commands - next command was type too early to [opensuse][krypton][wayland][x11regressions]test fails in kontact - Wrong synchronization between commands - next command was type too early
- Priority changed from Normal to High
Updated by nicksinger over 6 years ago
- Status changed from In Progress to Workable
- Assignee deleted (
nicksinger)
Sorry. I was not able to extract any more relevant infos out of this.
Updated by nicksinger over 6 years ago
- Subject changed from [opensuse][krypton][wayland][x11regressions]test fails in kontact - Wrong synchronization between commands - next command was type too early to [opensuse][krypton][wayland][x11regressions][hard] test fails in kontact - Wrong synchronization between commands - next command was type too early
Updated by mgriessmeier over 6 years ago
- Description updated (diff)
did a bit of debugging here
findings so far:
- When triggering 30 tests with excluding all modules except kontact, 30/30 succeeds
- cloning the job 30 times without excluding any modules, same behaviour as on o3
added H1 and H2
next steps:
trigger 30 jobs only loading the wayland module and kontact to test H2
Updated by mgriessmeier over 6 years ago
- Status changed from Workable to In Progress
H2 tests in progress...
Updated by mgriessmeier over 6 years ago
- Description updated (diff)
6/6 tests fail with the same issue when executing wayland test-modules before, so we can ACCEPT H2 I guess
it also seems like being related to https://bugzilla.suse.com/show_bug.cgi?id=1060990
Updated by okurz over 6 years ago
yes, could be related. I updated https://bugzilla.suse.com/show_bug.cgi?id=1060990#c2 with a link to this progress ticket here. Still, I think it is not the same issue and also won't be fixed unless we help to investigate further.
The most recent failure in kontact shows something different than the initial observation in this ticket: The word "kontact" is fully typed but apparently the "enter" key is not accepted. Did you also reproduce that or the original observation that only one character is typed in krunner?
Updated by mgriessmeier over 6 years ago
- Status changed from In Progress to Resolved
updated https://bugzilla.suse.com/show_bug.cgi?id=1060990 accordingly, no actions needs to be taken from openQA side -> resolved