Project

General

Profile

coordination #43889

[qe-core][epic][functional][virtio][wayland] openQA makes spelling mistakes

Added by szarate over 4 years ago. Updated 4 months ago.

Status:
Blocked
Priority:
Normal
Assignee:
-
Category:
Bugs in existing tests
Target version:
SUSE QA - Milestone 30
Start date:
Due date:
% Done:

0%

Estimated time:
Difficulty:
hard

Description

Observation

While looking at the screenshot, openqa typed Hello World (from the logs), but in the screen Hello Wolrd is seen... causing the mismatch... 

[2018-11-15T22:51:12.695 CET] [debug] /var/lib/openqa/cache/openqa.suse.de/tests/sle/tests/x11/ooffice.pm:24 called utils::type_string_slow
[2018-11-15T22:51:12.695 CET] [debug] <<< testapi::type_string(string='Hello World!', max_interval=13, wait_screen_changes=0, wait_still_screen=0)
[2018-11-15T22:51:16.349 CET] [debug] /var/lib/openqa/cache/openqa.suse.de/tests/sle/tests/x11/ooffice.pm:25 called testapi::assert_screen
[2018-11-15T22:51:16.349 CET] [debug] <<< testapi::assert_screen(mustmatch='test-ooffice-2', timeout=30)

openQA test in scenario sle-15-SP1-Installer-DVD-x86_64-gnome_sled@laptop_64bit-virtio-vga fails in
ooffice

Reproducible

Fails since (at least) Build 96.7 (current job)

Expected result

Last good: 95.1 (or more recent)

Further details

Always latest result in this scenario: latest

possible misstype ninjakeys

Related issues

Related to openQA Tests - action #43847: [functional][tools][u] test fails in zypper_lifecycle - Possible missing keys on GrenacheRejected2018-11-15

Related to openQA Tests - action #25618: [tools] test fails in zypper_lifecycle - Missing keys on openqaworker-arm-3Rejected2017-09-27

Related to openQA Tests - 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 promptRejected2018-11-26

Related to openQA Tests - action #20628: [opensuse][functional][u] test fails in chrome - Missing keys typing "about:". The SUT got "bout"Rejected2017-07-20

Related to openQA Tests - action #36355: [desktop][sle15sp1] test fails in gnome_music - missed characters while typing in xtermResolved2018-05-18

Related to openQA Tests - action #44600: [opensuse][desktop][sporadic] test fails in tracker_search_in_nautilus - missed keystroke to close nautilusResolved2018-11-30

Related to openQA Tests - action #46190: [functional][u] test fails in user_settings - mistyping in Username (lowercase instead of uppercase) Resolved2019-01-15

Related to openQA Tests - action #53639: [functional][u][sporadic] test fails in tracker_search_in_nautilus (missing keys)Resolved2019-07-02

Related to openQA Project - action #55703: send_keys() doesn't guarantee that the application will handle modifiers+normal_key properlyResolved2019-04-15

Related to openQA Tests - action #59026: [functional][u] test fails in firefox - command and argument mistypedRejected2019-11-04

Related to openQA Tests - action #58948: [sporadic][aarch64][ppc64le] missing first character in passed cmd string: e.g. 'ypper' rather than 'zypper' typed stringNew2019-10-31

Related to openQA Tests - action #90008: [qe-core][typing] test fails in ncurses with typing issues - Improve by using serial_terminal and executing tests via bashResolved

Related to openQA Tests - action #61820: [opensuse][kde][typing][functional][aarch64] test fails in grub_test on kde-live_installationRejected

Related to openQA Tests - action #67720: [qe-core][opensuse][typing] lost characters versus passed string of assert_script_run for ppc64 TW 20200602Resolved

Related to openQA Tests - action #91314: [opensuse][typing][sporadic][aarch64][ppc64le] repeated keys on aarc64 or ppc64le: Leap 15.3: test fails in repos - zzzypper command not foundNew

Related to openQA Tests - action #91299: [opensuse][kde][sporadic][typing] Leap: 15.3 test fails in firewall_enabled got firewaaaaaaaaaaaaaaa ..... instead of firewalldRejected

Related to openQA Project - action #113441: Try to mitigate "VNC typing issues" with disabled key repeat in linux tty's of qemu testsNew

Related to openQA Tests - action #109737: [opensuse][sporadic] test fails in chromium due to lost characters when typing in the address bar size:MResolved2022-04-09

Related to openQA Tests - action #125843: [qe-core][functional]test fails in xterm. some typed characters are missingResolved2023-03-13

Has duplicate openQA Tests - action #56150: test fails in gimpRejected2019-08-30

Has duplicate openQA Tests - action #57011: test fails in multi_users_dm - typed wrong commandRejected2019-09-18

Has duplicate openQA Tests - action #44051: [opensuse][functional][u][ppc64le][mistyping] gnucash failed as missed characters on xtermRejected2018-11-20

Has duplicate openQA Tests - action #60257: [functional][u][mistyping] random typing issues on waylandRejected2019-11-25

Has duplicate openQA Tests - action #76801: [qe-core] test ails in rrdtool_x11 - Missing characters typing rrdtoolRejected2020-10-30

Blocked by 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"Resolved2018-10-12

Blocks openQA Tests - action #48380: [qe-core][opensuse][functional][aarch64][sporadic] test fails in multiple modules on cryptlvm test - lost keystrokesBlocked2019-02-25

Blocks openQA Tests - action #54914: [Leap-15.4][qe-core][functional] Mistyping in some modules: vlc, x_vt (formerly xorg_vt), etc.New2019-07-31

History

#1 Updated by okurz over 4 years ago

As in IRC: I don't think it's qemu performance because we see spelling mistakes in ooffice more likely. I assume it's actually how the software behaves and what it does when you type in the background, e.g. automatic spell check and such. Unfortunate if the "spell check" actually causes the spelling mistakes :D We have seen something similar in krunner which depending on the incremental typing tries to find suggestions for what to open

#2 Updated by okurz over 4 years ago

Have you applied a needle to work around that issue already? the latest still points to the incomplete from 15h ago.

#3 Updated by szarate over 4 years ago

I disagree about this not being a qemu problem, I'm seeing a lot of misstypes and missing keys, ninja keys of all sorts... this could be that the wrong thing got to the SUT.

#4 Updated by szarate over 4 years ago

PS: Workaround needle created

#5 Updated by okurz over 4 years ago

szarate wrote:

I disagree about this not being a qemu problem, I'm seeing a lot of misstypes and missing keys, ninja keys of all sorts... this could be that the wrong thing got to the SUT.

Then please link the related tickets. The last time we worked on "ninja keys" we were nowhere to fixing it until we tried to separate concerns while still trying to keep the relations in mind.

#6 Updated by okurz over 4 years ago

  • Assignee set to szarate
  • Priority changed from Normal to High
  • Target version set to Milestone 21

szarate, assigning to you assuming the memory is still fresh, please see my last comment

#7 Updated by szarate over 4 years ago

okurz sure :)

#8 Updated by szarate over 4 years ago

  • Related to action #43847: [functional][tools][u] test fails in zypper_lifecycle - Possible missing keys on Grenache added

#9 Updated by szarate over 4 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

#10 Updated by szarate over 4 years ago

  • Related to action #25618: [tools] test fails in zypper_lifecycle - Missing keys on openqaworker-arm-3 added

#11 Updated by szarate over 4 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

#12 Updated by szarate over 4 years ago

This looks like a missed key press: https://openqa.suse.de/tests/2279310

#13 Updated by szarate over 4 years ago

Also happens here (ret key was pressed, but SUT didn't get it..): https://openqa.suse.de/tests/2296251

#14 Updated by szarate over 4 years ago

There's another poem missing here: https://openqa.suse.de/tests/2315968#step/firefox/4
and then same job, different test module: https://openqa.suse.de/tests/2315968#step/wireshark/72 (ctrl + / missed, therefore filter is not on focus, and then another poem is missing...)

#15 Updated by szarate over 4 years ago

another spelling mistake, https://openqa.suse.de/tests/2318579#comments looks like the spelling mistakes are more for virtio-gpu. I wonder what the rate would be and if this happens in regular x86_64...

#16 Updated by szarate over 4 years ago

  • Related to action #20628: [opensuse][functional][u] test fails in chrome - Missing keys typing "about:". The SUT got "bout" added

#17 Updated by szarate over 4 years ago

  • Related to action #36355: [desktop][sle15sp1] test fails in gnome_music - missed characters while typing in xterm added

#18 Updated by szarate over 4 years ago

  • Related to action #44600: [opensuse][desktop][sporadic] test fails in tracker_search_in_nautilus - missed keystroke to close nautilus added

#19 Updated by szarate over 4 years ago

  • Category changed from Bugs in existing tests to Spike/Research
  • Target version changed from Milestone 21 to Milestone 23
  • Difficulty set to hard

Moving this to a different milestone, as I don' t think we need to work on this right now. On the other hand, while it' s a bug per se... I think Okurz assumption that this is due to a problem with spell checking is misleading, and I' m starting to thing that this all is related to system load + qemu event key qeues not being processed correctly.

Also changing it to research :) Because there's some research needed...

#20 Updated by okurz over 4 years ago

  • Category changed from Spike/Research to Bugs in existing tests
  • Status changed from New to Blocked

I don't know who introduced the category which I think can be very misleading, especially because it's not described on the wiki as the other categories. Also, just because we need research which I definitely agree with, this is not a Research ticket, it really is "Bugs in existing tests" because tests fail. However, there is #42362 which zgao is working on – and he is conducting "Research" ;) - so I set this ticket to "Blocked" as we can wait for #42362, agreed? I am tracking the other ticket so feel free to assign to me for tracking.

#21 Updated by szarate over 4 years ago

so I set this ticket to "Blocked" as we can wait for #42362, agreed? I am tracking the other ticket so feel free to assign to me for tracking.

Not really agreed but I also won't work on this yet.

Hopefully you're able to understand why I'm linking so many tickets to this one ;) that has ninjakeys somewhere in the description.

#23 Updated by szarate over 4 years ago

on https://openqa.suse.de/tests/2382250:

SUT failed to 'get' the ret key event...

[2019-01-16T11:46:43.765 CET] [debug] >>> testapi::_handle_found_needle: found bootmenu-jeos-uefi-20180202, similarity 1.00 @ 195/263
[2019-01-16T11:46:43.765 CET] [debug] /var/lib/openqa/cache/openqa.suse.de/tests/sle/tests/installation/grub_test.pm:92 called bootloader_setup::stop_grub_timeout
[2019-01-16T11:46:43.765 CET] [debug] <<< testapi::send_key(key='up', do_wait=0)
[2019-01-16T11:46:43.971 CET] [debug] /var/lib/openqa/cache/openqa.suse.de/tests/sle/tests/installation/grub_test.pm:103 called testapi::send_key
[2019-01-16T11:46:43.971 CET] [debug] <<< testapi::send_key(key='ret', do_wait=0)
[2019-01-16T11:46:44.176 CET] [debug] ||| finished grub_test installation at 2019-01-16 10:46:44 (8 s)
[2019-01-16T11:46:44.177 CET] [debug] ||| starting first_boot tests/installation/first_boot.pm

#24 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: default@svirt-hyperv-uefi
https://openqa.suse.de/tests/2407255

#25 Updated by okurz over 4 years ago

  • Blocks action #44051: [opensuse][functional][u][ppc64le][mistyping] gnucash failed as missed characters on xterm added

#26 Updated by mgriessmeier about 4 years ago

  • Target version changed from Milestone 23 to Milestone 24

moving to M24

#27 Updated by SLindoMansilla about 4 years ago

  • Related to deleted (action #42362: [qe-core][qem][virtio][sle15sp0][sle15sp1][desktop][typing] test fails in window_system because "typing string is too fast in wayland")

#28 Updated by SLindoMansilla about 4 years ago

  • Blocked by action #42362: [qe-core][qem][virtio][sle15sp0][sle15sp1][desktop][typing] test fails in window_system because "typing string is too fast in wayland" added

#29 Updated by mgriessmeier about 4 years ago

  • Target version changed from Milestone 24 to Milestone 25

#30 Updated by szarate about 4 years ago

  • Target version changed from Milestone 25 to future

#31 Updated by szarate about 4 years ago

  • Assignee deleted (szarate)
  • Priority changed from High to Normal

We know this is here... There's so much we can do atm.

#32 Updated by okurz almost 4 years ago

  • Related to action #46190: [functional][u] test fails in user_settings - mistyping in Username (lowercase instead of uppercase) added

#33 Updated by SLindoMansilla almost 4 years ago

  • Blocks action #53639: [functional][u][sporadic] test fails in tracker_search_in_nautilus (missing keys) added

#34 Updated by SLindoMansilla almost 4 years ago

  • Blocks deleted (action #53639: [functional][u][sporadic] test fails in tracker_search_in_nautilus (missing keys))

#35 Updated by SLindoMansilla almost 4 years ago

  • Related to action #53639: [functional][u][sporadic] test fails in tracker_search_in_nautilus (missing keys) added

#36 Updated by SLindoMansilla almost 4 years ago

  • Related to action #54422: [functional][u] LO recent documents: alt-f not working on wayland (TW) added

#37 Updated by SLindoMansilla almost 4 years ago

  • Blocks action #48380: [qe-core][opensuse][functional][aarch64][sporadic] test fails in multiple modules on cryptlvm test - lost keystrokes added

#38 Updated by SLindoMansilla almost 4 years ago

  • Target version changed from future to Milestone 30+

Take a look in some months

#39 Updated by SLindoMansilla almost 4 years ago

  • Related to deleted (action #54422: [functional][u] LO recent documents: alt-f not working on wayland (TW))

#40 Updated by SLindoMansilla almost 4 years ago

  • Related to action #55703: send_keys() doesn't guarantee that the application will handle modifiers+normal_key properly added

#41 Updated by SLindoMansilla almost 4 years ago

Ticket for improving send_keys to send keys one after another and not at all at the same time: #55703

#42 Updated by SLindoMansilla almost 4 years ago

#43 Updated by SLindoMansilla over 3 years ago

  • Blocks action #54914: [Leap-15.4][qe-core][functional] Mistyping in some modules: vlc, x_vt (formerly xorg_vt), etc. added

#44 Updated by SLindoMansilla over 3 years ago

  • Has duplicate action #57011: test fails in multi_users_dm - typed wrong command added

#46 Updated by okurz over 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: gnome@uefi
https://openqa.opensuse.org/tests/1068181

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

#47 Updated by okurz over 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: zdup-Leap-15.0-gnome@64bit_cirrus
https://openqa.opensuse.org/tests/1080543

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

#48 Updated by SLindoMansilla over 3 years ago

  • Related to action #59026: [functional][u] test fails in firefox - command and argument mistyped added

#49 Updated by okurz over 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: desktopapps-documentation-x11
https://openqa.opensuse.org/tests/1093719

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

#50 Updated by dzedro over 3 years ago

  • Related to action #60257: [functional][u][mistyping] random typing issues on wayland added

#51 Updated by szarate over 3 years ago

  • Related to action #58948: [sporadic][aarch64][ppc64le] missing first character in passed cmd string: e.g. 'ypper' rather than 'zypper' typed string added

#52 Updated by okurz over 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: gnome-live
https://openqa.opensuse.org/tests/1107003

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

#53 Updated by zluo over 3 years ago

http://f40.suse.de/tests/5675#step/ooffice/6 seems that spelling issue is gone.

#54 Updated by okurz over 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: desktopapps-documentation-x11
https://openqa.opensuse.org/tests/1122525

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

#55 Updated by mgriessmeier over 3 years ago

  • Target version changed from Milestone 30+ to Milestone 30

needs to be discussed offline

#56 Updated by okurz over 3 years ago

  • Subject changed from [functional][u] test fails in ooffice - openQA makes spelling mistakes to [functional][u][virtio][wayland] test fails in ooffice - openQA makes spelling mistakes

mgriessmeier IMHO you should just assign yourself, track "Blocked" on #42362, the real ticket.

#57 Updated by okurz over 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: gnome
https://openqa.opensuse.org/tests/1167019

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

#58 Updated by okurz over 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: desktopapps-documentation
https://openqa.opensuse.org/tests/1187788

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

#59 Updated by okurz about 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: desktopapps-documentation
https://openqa.opensuse.org/tests/1199755

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

#60 Updated by okurz about 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: gnome@64bit-2G
https://openqa.opensuse.org/tests/1212422

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

#61 Updated by okurz about 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: gnome@64bit-2G
https://openqa.opensuse.org/tests/1234079

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

#62 Updated by okurz about 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: system_performance
https://openqa.suse.de/tests/4174649

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

#63 Updated by SLindoMansilla about 3 years ago

  • Blocks deleted (action #44051: [opensuse][functional][u][ppc64le][mistyping] gnucash failed as missed characters on xterm)

#64 Updated by SLindoMansilla about 3 years ago

  • Has duplicate action #44051: [opensuse][functional][u][ppc64le][mistyping] gnucash failed as missed characters on xterm added

#65 Updated by SLindoMansilla about 3 years ago

  • Related to deleted (action #60257: [functional][u][mistyping] random typing issues on wayland)

#66 Updated by SLindoMansilla about 3 years ago

  • Has duplicate action #60257: [functional][u][mistyping] random typing issues on wayland added

#67 Updated by okurz about 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: gnome@64bit-2G
https://openqa.opensuse.org/tests/1267135

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

#68 Updated by okurz about 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: gnome@64bit-2G
https://openqa.opensuse.org/tests/1283018

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

#69 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: gnome
https://openqa.opensuse.org/tests/1303067

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

#70 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: desktopapps-documentation
https://openqa.opensuse.org/tests/1320929

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

#71 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: desktopapps-documentation
https://openqa.opensuse.org/tests/1341552

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

#72 Updated by okurz over 2 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: desktopapps-documentation
https://openqa.opensuse.org/tests/1431510

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

#73 Updated by okurz over 2 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: desktopapps-documentation
https://openqa.opensuse.org/tests/1450732

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

#74 Updated by szarate over 2 years ago

  • Has duplicate action #76801: [qe-core] test ails in rrdtool_x11 - Missing characters typing rrdtool added

#75 Updated by tjyrinki_suse over 2 years ago

  • Subject changed from [functional][u][virtio][wayland] test fails in ooffice - openQA makes spelling mistakes to [qe-core][functional][virtio][wayland] test fails in ooffice - openQA makes spelling mistakes

#76 Updated by okurz over 2 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: desktopapps-documentation
https://openqa.opensuse.org/tests/1479674

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

#77 Updated by okurz over 2 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: wsm+dev_tools+textmode
https://openqa.suse.de/tests/5130599

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

#78 Updated by okurz over 2 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: desktopapps-documentation
https://openqa.opensuse.org/tests/1513606

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

#79 Updated by okurz over 2 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: textmode+role_textmode
https://openqa.suse.de/tests/5211304

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

#80 Updated by okurz over 2 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: desktopapps-documentation
https://openqa.opensuse.org/tests/1591524

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

#81 Updated by okurz over 2 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: desktopapps-documentation-x11
https://openqa.opensuse.org/tests/1611768

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

#82 Updated by okurz over 2 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: desktopapps-documentation
https://openqa.opensuse.org/tests/1626687

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

#83 Updated by okurz over 2 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: wsm+dev_tools+textmode
https://openqa.suse.de/tests/5552818

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

#84 Updated by okurz about 2 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: desktopapps-documentation
https://openqa.opensuse.org/tests/1667943

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

#85 Updated by okurz about 2 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: desktopapps-documentation
https://openqa.opensuse.org/tests/1684118

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

#86 Updated by okurz about 2 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: desktopapps-documentation-wayland
https://openqa.opensuse.org/tests/1693311

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

#87 Updated by openqa_review about 2 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: desktopapps-documentation-wayland
https://openqa.opensuse.org/tests/1693311

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

#88 Updated by tjyrinki_suse about 2 years ago

  • Tracker changed from action to coordination
  • Subject changed from [qe-core][functional][virtio][wayland] test fails in ooffice - openQA makes spelling mistakes to [qe-core][epic][functional][virtio][wayland] openQA makes spelling mistakes
  • Start date deleted (2018-11-16)

#89 Updated by tjyrinki_suse about 2 years ago

  • Related to action #90008: [qe-core][typing] test fails in ncurses with typing issues - Improve by using serial_terminal and executing tests via bash added

#90 Updated by tjyrinki_suse about 2 years ago

  • Related to action #61820: [opensuse][kde][typing][functional][aarch64] test fails in grub_test on kde-live_installation added

#91 Updated by tjyrinki_suse about 2 years ago

  • Related to action #67720: [qe-core][opensuse][typing] lost characters versus passed string of assert_script_run for ppc64 TW 20200602 added

#92 Updated by tjyrinki_suse about 2 years ago

  • Related to action #91314: [opensuse][typing][sporadic][aarch64][ppc64le] repeated keys on aarc64 or ppc64le: Leap 15.3: test fails in repos - zzzypper command not found added

#93 Updated by tjyrinki_suse about 2 years ago

  • Related to action #91299: [opensuse][kde][sporadic][typing] Leap: 15.3 test fails in firewall_enabled got firewaaaaaaaaaaaaaaa ..... instead of firewalld added

#94 Updated by okurz about 2 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: extra_tests_gnome
https://openqa.suse.de/tests/5990437

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

#95 Updated by okurz about 2 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: extra_tests_gnome
https://openqa.suse.de/tests/5990437

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

#96 Updated by okurz almost 2 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: extra_tests_gnome
https://openqa.suse.de/tests/5990437

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

#97 Updated by okurz almost 2 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: extra_tests_gnome
https://openqa.suse.de/tests/5990437

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" or "EOL" (End-of-Life)
  3. The label in the openQA scenario is removed

#98 Updated by openqa_review almost 2 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: extra_tests_gnome
https://openqa.suse.de/tests/5990437

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" or "EOL" (End-of-Life)
  3. The label in the openQA scenario is removed

#99 Updated by openqa_review almost 2 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: desktopapps-documentation
https://openqa.opensuse.org/tests/1854537

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" or "EOL" (End-of-Life)
  3. The label in the openQA scenario is removed

#100 Updated by openqa_review almost 2 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: desktopapps-documentation
https://openqa.opensuse.org/tests/1870957

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" or "EOL" (End-of-Life)
  3. The label in the openQA scenario is removed

#101 Updated by openqa_review almost 2 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: desktopapps-documentation
https://openqa.opensuse.org/tests/1881632

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" or "EOL" (End-of-Life)
  3. The label in the openQA scenario is removed

#102 Updated by openqa_review almost 2 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: desktopapps-documentation-wayland
https://openqa.opensuse.org/tests/1898078

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" or "EOL" (End-of-Life)
  3. The label in the openQA scenario is removed

#103 Updated by openqa_review over 1 year ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: desktopapps-documentation
https://openqa.opensuse.org/tests/1925631

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" or "EOL" (End-of-Life)
  3. The bugref in the openQA scenario is removed or replaced, e.g. label:wontfix:boo1234

#104 Updated by openqa_review over 1 year ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: toolkits
https://openqa.suse.de/tests/7364362

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" or "EOL" (End-of-Life)
  3. The bugref in the openQA scenario is removed or replaced, e.g. label:wontfix:boo1234

#105 Updated by openqa_review over 1 year ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: upgrade_Leap_15.0_cryptlvm@uefi
https://openqa.opensuse.org/tests/2041724

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" or "EOL" (End-of-Life)
  3. The bugref in the openQA scenario is removed or replaced, e.g. label:wontfix:boo1234

#106 Updated by openqa_review over 1 year ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: desktopapps-documentation
https://openqa.opensuse.org/tests/2150931

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" or "EOL" (End-of-Life)
  3. The bugref in the openQA scenario is removed or replaced, e.g. label:wontfix:boo1234

#107 Updated by openqa_review about 1 year ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: desktopapps-documentation
https://openqa.opensuse.org/tests/2405013

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" or "EOL" (End-of-Life)
  3. The bugref in the openQA scenario is removed or replaced, e.g. label:wontfix:boo1234

Expect the next reminder at the earliest in 268 days if nothing changes in this ticket.

#108 Updated by okurz 11 months ago

  • Related to action #113441: Try to mitigate "VNC typing issues" with disabled key repeat in linux tty's of qemu tests added

#109 Updated by openqa_review 11 months ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: desktopapps-documentation
https://openqa.opensuse.org/tests/2461612

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" or "EOL" (End-of-Life)
  3. The bugref in the openQA scenario is removed or replaced, e.g. label:wontfix:boo1234

Expect the next reminder at the earliest in 28 days if nothing changes in this ticket.

#110 Updated by openqa_review 11 months ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: desktopapps-documentation
https://openqa.opensuse.org/tests/2480150

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" or "EOL" (End-of-Life)
  3. The bugref in the openQA scenario is removed or replaced, e.g. label:wontfix:boo1234

Expect the next reminder at the earliest in 28 days if nothing changes in this ticket.

#111 Updated by openqa_review 10 months ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: desktopapps-documentation-x11
https://openqa.opensuse.org/tests/2538093

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" or "EOL" (End-of-Life)
  3. The bugref in the openQA scenario is removed or replaced, e.g. label:wontfix:boo1234

Expect the next reminder at the earliest in 56 days if nothing changes in this ticket.

#112 Updated by openqa_review 8 months ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: desktopapps-documentation
https://openqa.opensuse.org/tests/2809749

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" or "EOL" (End-of-Life)
  3. The bugref in the openQA scenario is removed or replaced, e.g. label:wontfix:boo1234

Expect the next reminder at the earliest in 112 days if nothing changes in this ticket.

#113 Updated by okurz 4 months ago

  • Related to action #109737: [opensuse][sporadic] test fails in chromium due to lost characters when typing in the address bar size:M added

#114 Updated by openqa_review 4 months ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: desktopapps-documentation-x11
https://openqa.opensuse.org/tests/3069209

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" or "EOL" (End-of-Life)
  3. The bugref in the openQA scenario is removed or replaced, e.g. label:wontfix:boo1234

Expect the next reminder at the earliest in 28 days if nothing changes in this ticket.

#115 Updated by openqa_review 4 months ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: desktopapps-documentation
https://openqa.opensuse.org/tests/3107276

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" or "EOL" (End-of-Life)
  3. The bugref in the openQA scenario is removed or replaced, e.g. label:wontfix:boo1234

Expect the next reminder at the earliest in 28 days if nothing changes in this ticket.

#116 Updated by ph03nix 2 months ago

  • Related to action #125843: [qe-core][functional]test fails in xterm. some typed characters are missing added

Also available in: Atom PDF