coordination #43889
open[qe-core][epic][functional][virtio][wayland] openQA makes spelling mistakes
Added by szarate over 5 years ago. Updated about 2 months ago.
0%
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
Updated by okurz over 5 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
Updated by okurz over 5 years ago
Have you applied a needle to work around that issue already? the latest still points to the incomplete from 15h ago.
Updated by szarate over 5 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.
Updated by okurz over 5 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.
Updated by okurz over 5 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
Updated by szarate over 5 years ago
- Related to action #43847: [functional][tools][u] test fails in zypper_lifecycle - Possible missing keys on Grenache added
Updated by szarate over 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
Updated by szarate over 5 years ago
- Related to action #25618: [tools] test fails in zypper_lifecycle - Missing keys on openqaworker-arm-3 added
Updated by szarate over 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
Updated by szarate over 5 years ago
This looks like a missed key press: https://openqa.suse.de/tests/2279310
Updated by szarate over 5 years ago
Also happens here (ret key was pressed, but SUT didn't get it..): https://openqa.suse.de/tests/2296251
Updated by szarate over 5 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...)
Updated by szarate over 5 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...
Updated by szarate over 5 years ago
- Related to action #20628: [opensuse][functional][u] test fails in chrome - Missing keys typing "about:". The SUT got "bout" added
Updated by szarate over 5 years ago
- Related to action #36355: [desktop][sle15sp1] test fails in gnome_music - missed characters while typing in xterm added
Updated by szarate over 5 years ago
- Related to action #44600: [opensuse][desktop][sporadic] test fails in tracker_search_in_nautilus - missed keystroke to close nautilus added
Updated by szarate over 5 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...
Updated by okurz over 5 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.
Updated by szarate over 5 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.
Updated by oorlov over 5 years ago
Just for more statistics, another spelling mistakes:
https://openqa.suse.de/tests/2329369#step/ooffice/6
https://openqa.suse.de/tests/2329369#step/firefox/4
Updated by szarate over 5 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
Updated by okurz over 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: default@svirt-hyperv-uefi
https://openqa.suse.de/tests/2407255
Updated by okurz about 5 years ago
- Blocks action #44051: [opensuse][functional][u][ppc64le][mistyping] gnucash failed as missed characters on xterm added
Updated by mgriessmeier about 5 years ago
- Target version changed from Milestone 23 to Milestone 24
moving to M24
Updated by SLindoMansilla about 5 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")
Updated by SLindoMansilla about 5 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
Updated by mgriessmeier almost 5 years ago
- Target version changed from Milestone 24 to Milestone 25
Updated by szarate almost 5 years ago
- Target version changed from Milestone 25 to future
Updated by szarate almost 5 years ago
- Assignee deleted (
szarate) - Priority changed from High to Normal
We know this is here... There's so much we can do atm.
Updated by okurz almost 5 years ago
- Related to action #46190: [functional][u] test fails in user_settings - mistyping in Username (lowercase instead of uppercase) added
Updated by SLindoMansilla over 4 years ago
- Blocks action #53639: [functional][u][sporadic] test fails in tracker_search_in_nautilus (missing keys) added
Updated by SLindoMansilla over 4 years ago
- Blocks deleted (action #53639: [functional][u][sporadic] test fails in tracker_search_in_nautilus (missing keys))
Updated by SLindoMansilla over 4 years ago
- Related to action #53639: [functional][u][sporadic] test fails in tracker_search_in_nautilus (missing keys) added
Updated by SLindoMansilla over 4 years ago
- Related to action #54422: [functional][u] LO recent documents: alt-f not working on wayland (TW) added
Updated by SLindoMansilla over 4 years ago
- Blocks action #48380: [qe-core][opensuse][functional][aarch64][sporadic] test fails in multiple modules on cryptlvm test - lost keystrokes added
Updated by SLindoMansilla over 4 years ago
- Target version changed from future to Milestone 30+
Take a look in some months
Updated by SLindoMansilla over 4 years ago
- Related to deleted (action #54422: [functional][u] LO recent documents: alt-f not working on wayland (TW))
Updated by SLindoMansilla over 4 years ago
- Related to action #55703: send_keys() doesn't guarantee that the application will handle modifiers+normal_key properly added
Updated by SLindoMansilla over 4 years ago
Ticket for improving send_keys to send keys one after another and not at all at the same time: #55703
Updated by SLindoMansilla over 4 years ago
- Has duplicate action #56150: test fails in gimp added
Updated by SLindoMansilla over 4 years ago
- Blocks action #54914: [Leap-15.4][qe-core][functional] Mistyping in some modules: vlc, x_vt (formerly xorg_vt), etc. added
Updated by SLindoMansilla over 4 years ago
- Has duplicate action #57011: test fails in multi_users_dm - typed wrong command added
Updated by SLindoMansilla over 4 years ago
Recent occurrence of spelling mistakes in https://openqa.opensuse.org/tests/1034571/modules/multi_users_dm/steps/19
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@uefi
https://openqa.opensuse.org/tests/1068181
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
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: 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:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
Updated by SLindoMansilla over 4 years ago
- Related to action #59026: [functional][u] test fails in firefox - command and argument mistyped added
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: desktopapps-documentation-x11
https://openqa.opensuse.org/tests/1093719
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
Updated by dzedro over 4 years ago
- Related to action #60257: [functional][u][mistyping] random typing issues on wayland added
Updated by szarate over 4 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
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-live
https://openqa.opensuse.org/tests/1107003
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
Updated by zluo over 4 years ago
http://f40.suse.de/tests/5675#step/ooffice/6 seems that spelling issue is gone.
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: desktopapps-documentation-x11
https://openqa.opensuse.org/tests/1122525
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
Updated by mgriessmeier over 4 years ago
- Target version changed from Milestone 30+ to Milestone 30
needs to be discussed offline
Updated by okurz over 4 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.
Updated by okurz about 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.opensuse.org/tests/1167019
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
Updated by okurz about 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: desktopapps-documentation
https://openqa.opensuse.org/tests/1187788
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
Updated by okurz about 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: desktopapps-documentation
https://openqa.opensuse.org/tests/1199755
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
Updated by okurz about 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@64bit-2G
https://openqa.opensuse.org/tests/1212422
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
Updated by okurz about 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@64bit-2G
https://openqa.opensuse.org/tests/1234079
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
Updated by okurz about 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: system_performance
https://openqa.suse.de/tests/4174649
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
Updated by SLindoMansilla almost 4 years ago
- Blocks deleted (action #44051: [opensuse][functional][u][ppc64le][mistyping] gnucash failed as missed characters on xterm)
Updated by SLindoMansilla almost 4 years ago
- Has duplicate action #44051: [opensuse][functional][u][ppc64le][mistyping] gnucash failed as missed characters on xterm added
Updated by SLindoMansilla almost 4 years ago
- Related to deleted (action #60257: [functional][u][mistyping] random typing issues on wayland)
Updated by SLindoMansilla almost 4 years ago
- Has duplicate action #60257: [functional][u][mistyping] random typing issues on wayland added
Updated by okurz almost 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@64bit-2G
https://openqa.opensuse.org/tests/1267135
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
Updated by okurz almost 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@64bit-2G
https://openqa.opensuse.org/tests/1283018
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
Updated by okurz almost 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.opensuse.org/tests/1303067
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
Updated by okurz almost 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: desktopapps-documentation
https://openqa.opensuse.org/tests/1320929
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
Updated by okurz almost 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: desktopapps-documentation
https://openqa.opensuse.org/tests/1341552
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
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/1431510
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
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/1450732
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
Updated by szarate over 3 years ago
- Has duplicate action #76801: [qe-core] test ails in rrdtool_x11 - Missing characters typing rrdtool added
Updated by tjyrinki_suse over 3 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
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/1479674
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
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: wsm+dev_tools+textmode
https://openqa.suse.de/tests/5130599
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
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/1513606
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
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: textmode+role_textmode
https://openqa.suse.de/tests/5211304
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
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/1591524
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
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/1611768
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
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/1626687
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
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: wsm+dev_tools+textmode
https://openqa.suse.de/tests/5552818
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
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/1667943
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
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/1684118
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
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-wayland
https://openqa.opensuse.org/tests/1693311
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
Updated by openqa_review 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-wayland
https://openqa.opensuse.org/tests/1693311
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
Updated by tjyrinki_suse about 3 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)
Updated by tjyrinki_suse about 3 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
Updated by tjyrinki_suse about 3 years ago
- Related to action #61820: [opensuse][kde][typing][functional][aarch64] test fails in grub_test on kde-live_installation added
Updated by tjyrinki_suse about 3 years ago
- Related to action #67720: [qe-core][opensuse][typing] lost characters versus passed string of assert_script_run for ppc64 TW 20200602 added
Updated by tjyrinki_suse about 3 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
Updated by tjyrinki_suse about 3 years ago
- Related to action #91299: [opensuse][kde][sporadic][typing] Leap: 15.3 test fails in firewall_enabled got firewaaaaaaaaaaaaaaa ..... instead of firewalld added
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: extra_tests_gnome
https://openqa.suse.de/tests/5990437
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
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: extra_tests_gnome
https://openqa.suse.de/tests/5990437
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
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: extra_tests_gnome
https://openqa.suse.de/tests/5990437
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
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: extra_tests_gnome
https://openqa.suse.de/tests/5990437
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- The label in the openQA scenario is removed
Updated by openqa_review 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: extra_tests_gnome
https://openqa.suse.de/tests/5990437
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- The label in the openQA scenario is removed
Updated by openqa_review 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/1854537
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- The label in the openQA scenario is removed
Updated by openqa_review 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/1870957
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- The label in the openQA scenario is removed
Updated by openqa_review 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/1881632
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- The label in the openQA scenario is removed
Updated by openqa_review 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-wayland
https://openqa.opensuse.org/tests/1898078
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- The label in the openQA scenario is removed
Updated by openqa_review 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/1925631
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- The bugref in the openQA scenario is removed or replaced, e.g.
label:wontfix:boo1234
Updated by openqa_review 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: toolkits
https://openqa.suse.de/tests/7364362
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- The bugref in the openQA scenario is removed or replaced, e.g.
label:wontfix:boo1234
Updated by openqa_review 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: 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:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- The bugref in the openQA scenario is removed or replaced, e.g.
label:wontfix:boo1234
Updated by openqa_review 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/2150931
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- The bugref in the openQA scenario is removed or replaced, e.g.
label:wontfix:boo1234
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/2405013
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- 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.
Updated by okurz almost 2 years ago
- Related to action #113441: Try to mitigate "VNC typing issues" with disabled key repeat in linux tty's of qemu tests added
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/2461612
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- 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.
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/2480150
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- 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.
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-x11
https://openqa.opensuse.org/tests/2538093
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- 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.
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/2809749
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- 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.
Updated by okurz over 1 year ago
- Related to action #109737: [opensuse][sporadic] test fails in chromium due to lost characters when typing in the address bar size:M added
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-x11
https://openqa.opensuse.org/tests/3069209
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- 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.
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/3107276
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- 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.
Updated by ph03nix about 1 year ago
- Related to action #125843: [qe-core][functional]test fails in xterm. some typed characters are missing added
Updated by openqa_review 2 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: gnome@
https://openqa.opensuse.org/tests/3972485
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- 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.
Updated by okurz about 2 months ago
https://bugzilla.suse.com/show_bug.cgi?id=1117882 was RESOLVED referencing a commit (in qemu or kernel?) that should improve the situation with keyup events mappings hence should have an impact in case of mistyping or "spelling mistakes". However my experience from the past years is that any such problems left with lost or mistyped characters at least on x86_64 qemu based tests are always application specific behaviour. So I recommend to look into the application specific problems and handle accordingly in the test code.