action #33283
[opensuse][functional][u][sporadic][medium] test fails in kontact - typing string loosing characters
0%
Description
Related issues
History
#1
Updated by okurz over 4 years ago
- 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
#2
Updated by okurz over 4 years ago
- Target version set to Milestone 16
something to look for after #30805
#3
Updated by zluo over 4 years ago
compared with successful run: https://openqa.opensuse.org/tests/609894#step/kontact/13
It is a problem with mistyping. I check the history and found this problem happened many times in the past.
#4
Updated by okurz about 4 years ago
- Has duplicate action #34363: test fails in kontact added
#5
Updated by okurz about 4 years ago
- Subject changed from [opensuse tw][functional] test fails in kontact - typing string loosing characters to [opensuse][functional][u] test fails in kontact - typing string loosing characters
- Due date set to 2018-05-08
- Priority changed from Normal to High
Latest report from lnussel about Leap 15.0:
Observation¶
openQA test in scenario opensuse-15.0-DVD-x86_64-kde-wayland@64bit_virtio-2G fails in
kontact
looking at the video x11_start_program seems to be unreliable with wayland. it mistypes the command and starts random progams. no idea why it always hits the kontact test though :)
Reproducible¶
Fails since (at least) Build 156.1
Further details¶
Always latest result in this scenario: latest
#6
Updated by mgriessmeier about 4 years ago
- Subject changed from [opensuse][functional][u] test fails in kontact - typing string loosing characters to [opensuse][functional][u][medium] test fails in kontact - typing string loosing characters
- Description updated (diff)
- Status changed from New to Workable
#7
Updated by cwh about 4 years ago
- Difficulty set to medium
#9
Updated by zluo about 4 years ago
- Status changed from Workable to In Progress
#10
Updated by JERiveraMoya about 4 years ago
I found this one in case you could have buffer on this ticket, I guess at the end we need to close that windows that is avoiding to match needles: #35589. It is not related with the typing and I think is also present in tw.
#11
Updated by zluo about 4 years ago
Yesterday it has problem with needle match on osd:
https://openqa.opensuse.org/tests/662767
but the problem with typing string doesn't happen anymore:
https://openqa.opensuse.org/tests/663701
and my local test run shows correct result as well:
http://e13.suse.de/tests/2172
#12
Updated by zluo about 4 years ago
will re-run the tests for 50 times and see if it still has problem or not.
#13
Updated by zluo about 4 years ago
till now with a lot of test run, I can say this issue is not reproducible.
#14
Updated by zluo about 4 years ago
checking on o3:
https://openqa.opensuse.org/tests/664925
#15
Updated by zluo about 4 years ago
force_cron_run from another test on o3 shows good result:
https://openqa.opensuse.org/tests/664925#step/force_cron_run
#16
Updated by zluo about 4 years ago
I found a different issue:
#17
Updated by zluo about 4 years ago
I found this record in bugzilla:
#18
Updated by zluo about 4 years ago
https://openqa.opensuse.org/tests/664926#step/kontact looks good however.
#19
Updated by zluo about 4 years ago
- Status changed from In Progress to Resolved
I don't see this problem anymore by re-tests o3 and my local server. Set is as resolved.
#20
Updated by okurz about 4 years ago
- Subject changed from [opensuse][functional][u][medium] test fails in kontact - typing string loosing characters to [opensuse][functional][u][sporadic][medium] test fails in kontact - typing string loosing characters
- Status changed from Resolved to In Progress
I don't know how you checked but checking the latest TW test immediately shows a failure in kontact: https://openqa.opensuse.org/tests/667728 and also the history shows that kontact fails like near every time except for the cases that the scenario already aborts in before, e.g. on oocalc.
#21
Updated by zluo about 4 years ago
this is a different issue which i mentioned already:
#22
Updated by zluo about 4 years ago
again, a lot of test runs didn't show this issue on my local server
and test run on osd:
#23
Updated by zluo about 4 years ago
- Status changed from In Progress to Resolved
#24
Updated by okurz almost 3 years ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: kde-wayland@64bit_virtio
https://openqa.opensuse.org/tests/1005564