Project

General

Profile

Actions
Copy link

action #60257

closed

[functional][u][mistyping] random typing issues on wayland

Added by dzedro almost 5 years ago. Updated over 4 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
mgriessmeier
Category:
Bugs in existing tests
Target version:
SUSE QA - Milestone 30
Start date:
2019-11-25
Due date:
% Done:

0%

Estimated time:
42.00 h
Difficulty:

Description

After QAMUVGA=cirrus is not default, tests use by default wayland, where issues with ninja keys started to be common.

https://openqa.suse.de/tests/3626853#step/ooffice/6
https://openqa.suse.de/tests/3626858#step/libreoffice_open_specified_file/70
https://openqa.suse.de/tests/3631026#step/ghostscript/22
https://openqa.suse.de/tests/3624774#step/yast2_snapper/43
https://openqa.suse.de/tests/3628683#step/gnome_music/5

Related issues 4 (1 open — 3 closed)

Related to openQA Tests - action #55445: [functional][u] On OSD get rid of workaround QEMUVGA=cirrus in machinesResolveddheidler2019-10-28

Actions
Related to openQA Tests - action #42362: [qe-core][qem][virtio][sle15sp0][sle15sp1][desktop][typing] test fails in window_system because "typing string is too fast in wayland"Resolvedzcjia2018-10-12

Actions
Related to openQA Infrastructure - action #139271: Repurpose PowerPC hardware in FC Basement - mania Power8 PowerPC size:MResolvedokurz2023-09-20

Actions
Is duplicate of openQA Tests - coordination #43889: [qe-core][epic][functional][virtio][wayland] openQA makes spelling mistakesBlocked

Actions
Actions
Copy link
 #1

Updated by dzedro almost 5 years ago

  • Related to action #55445: [functional][u] On OSD get rid of workaround QEMUVGA=cirrus in machines added
Actions
Copy link
 #2

Updated by dzedro almost 5 years ago

  • Related to action #44339: [functional][u][mistyping] test fails in sshxterm - character missing in tput bold 2; tput setaf 1 making the test fail due to the needle not matching the expected prompt added
Actions
Copy link
 #3

Updated by dzedro almost 5 years ago

  • Related to deleted (action #44339: [functional][u][mistyping] test fails in sshxterm - character missing in tput bold 2; tput setaf 1 making the test fail due to the needle not matching the expected prompt)
Actions
Copy link
 #4

Updated by dzedro almost 5 years ago

  • Related to coordination #43889: [qe-core][epic][functional][virtio][wayland] openQA makes spelling mistakes added
Actions
Copy link
 #5

Updated by zluo almost 5 years ago

  • Category set to Bugs in existing tests
  • Status changed from New to Workable
  • Target version set to Milestone 28
  • Estimated time set to 42.00 h

suggestion: to use VNC_TYPING_LIMIT for try.

Actions
Copy link
 #6

Updated by dheidler almost 5 years ago

  • Status changed from Workable to In Progress
  • Assignee set to dheidler
Actions
Copy link
 #7

Updated by dzedro almost 5 years ago

I added VNC_TYPING_LIMIT=18 on 15sp1 as it passed without mistype, tired multiple values, 15 works but on 20 there was still typing problem https://openqa.suse.de/tests/3646105#step/ghostscript/24
Will see if 18 is good enough or will try even lover limit.

Actions
Copy link
 #8

Updated by dheidler almost 5 years ago

I also had misstypings for value 20: http://artemis.suse.de/tests/2104#step/libreoffice_open_specified_file/13

According to https://de.wikipedia.org/wiki/Anschl%C3%A4ge_pro_Minute the world record of fast typing is at 15.9 keys per second.

Actions
Copy link
 #9

Updated by dheidler almost 5 years ago

  • Status changed from In Progress to Feedback

Added VNC_TYPING_LIMIT=18 to all test suites on osd matching ^gnome and to alpatterns

Actions
Copy link
 #10

Updated by dzedro almost 5 years ago

ghostscript test is failing with VNC_TYPING_LIMIT=10 https://openqa.suse.de/tests/3672654#settings
At the end I will have to modify test ghostscript, as for some reason typing is getting nuts there.

Actions
Copy link
 #11

Updated by dzedro almost 5 years ago

I would say there is issue on wayland which can't be reliably solved with VNC_TYPING_LIMIT, found typing failures with VNC_TYPING_LIMIT=10 https://openqa.suse.de/tests/3684650#step/libreoffice_double_click_file/104
I'm using even lover values, but it still didn't eliminate typing issue & another problem is that such low typing limit makes the test run much longer.

Actions
Copy link
 #12

Updated by mgriessmeier almost 5 years ago

  • Target version changed from Milestone 28 to Milestone 30

let's discuss this please :)

what is still needed?

Actions
Copy link
 #13

Updated by dheidler almost 5 years ago

Ideas:

  • Crosscheck if VM is busy or test environment (around VM)
  • Check IO activity from qemu
  • Cross check system responsiveness from post fail hook and magic sysrq
  • Ensure baseclass post fail hook executes first to check system responsiveness
Actions
Copy link
 #14

Updated by okurz almost 5 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: gnome
https://openqa.suse.de/tests/3806218

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released"
  3. The label in the openQA scenario is removed
Actions
Copy link
 #15

Updated by dheidler almost 5 years ago

  • Status changed from Feedback to Workable
  • Assignee deleted (dheidler)
Actions
Copy link
 #16

Updated by dheidler almost 5 years ago

Suggestion: use xdotool to type a lokg text into libreoffice and see if that works.

Actions
Copy link
 #17

Updated by okurz almost 5 years ago

  • Related to action #42362: [qe-core][qem][virtio][sle15sp0][sle15sp1][desktop][typing] test fails in window_system because "typing string is too fast in wayland" added
Actions
Copy link
 #18

Updated by okurz almost 5 years ago

  • Status changed from Workable to Blocked
  • Assignee set to mgriessmeier
  • Priority changed from Urgent to Normal

Actually I suggest no one invests any work specifically in this ticket unless it's module specific work arounds as the related ticket #43889 has many more related tickets and hence more information. #42362 is the ticket you should wait for.

@mgriessmeier maybe as QSF-u PO you want to assign this ticket to yourself and set to "Blocked"? You know, part of "saying No" as PO as in "We will not do it, wait for desktop experts" :) Please see my ticket assignment only as a suggestion, feel free to change it any way you like.

Actions
Copy link
 #19

Updated by openqa_review over 4 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: gnome
https://openqa.suse.de/tests/4020118

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released"
  3. The label in the openQA scenario is removed
Actions
Copy link
 #20

Updated by okurz over 4 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: gnome
https://openqa.suse.de/tests/4020118

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released"
  3. The label in the openQA scenario is removed
Actions
Copy link
 #21

Updated by okurz over 4 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: qam-allpatterns+addons@uefi
https://openqa.suse.de/tests/4091228

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released"
  3. The label in the openQA scenario is removed
Actions
Copy link
 #22

Updated by SLindoMansilla over 4 years ago

  • Related to deleted (coordination #43889: [qe-core][epic][functional][virtio][wayland] openQA makes spelling mistakes)
Actions
Copy link
 #23

Updated by SLindoMansilla over 4 years ago

  • Is duplicate of coordination #43889: [qe-core][epic][functional][virtio][wayland] openQA makes spelling mistakes added
Actions
Copy link
 #24

Updated by SLindoMansilla over 4 years ago

  • Status changed from Blocked to Rejected

As duplicate of #43889

Actions
Copy link
 #25

Updated by okurz about 1 year ago

  • Related to action #139271: Repurpose PowerPC hardware in FC Basement - mania Power8 PowerPC size:M added
Actions
Copy link

Also available in: Atom PDF