action #44180
closed
[sle][functional][u] test fails in keymap_or_locale - because typing issue
Added by zluo over 5 years ago.
Updated over 4 years ago.
Category:
Bugs in existing tests
Target version:
SUSE QA - Milestone 27
Description
As I can see that needle us_keymap couldn't match because of typing issue. '12345 are missing
Observation¶
openQA test in scenario sle-15-SP1-Installer-DVD-ppc64le-textmode@ppc64le fails in
keymap_or_locale
Reproducible¶
Fails since (at least) Build 100.4 (current job)
Expected result¶
Last good: 100.1 (or more recent)
Further details¶
Always latest result in this scenario: latest
- Related to action #36355: [desktop][sle15sp1] test fails in gnome_music - missed characters while typing in xterm added
- Related to action #20628: [opensuse][functional][u] test fails in chrome - Missing keys typing "about:". The SUT got "bout" added
- Related to action #18020: [sle][migration][backlog] test fails in hostname by typing uppercase commands added
- Related to action #31138: [tools][opensuse]test fails in yast2_control_center - loosing keys? added
- Target version set to Milestone 23
- Status changed from New to Workable
- Priority changed from Normal to High
- Target version changed from Milestone 23 to Milestone 22
- Status changed from Workable to In Progress
zluo wrote:
take over and check.
please assign yourself if you put the ticket to "in progress"
- Status changed from In Progress to Workable
- Assignee deleted (
zluo)
I won't be able to fix a typing issue which is related to qemu or performance. Can someone please take over?
let me find the "blocker"
- Related to action #47081: [hyperv] test fails in keymap_or_locale; some characters with shift not typed added
- Blocked by action #46508: [qe-core][functional] Ensure to use a clean "extra" console for keymap_or_locale and / or do not try to login (at least on local backends) added
- Status changed from Workable to Blocked
- Blocked by action #46532: [functional][u] test fails in keymap_or_locale as the test fails to unlock the screenlock when it should not even care about the displaymanager added
- Priority changed from High to Normal
- Target version changed from Milestone 22 to Milestone 25
- Assignee changed from okurz to mgriessmeier
Move to new QSF-u PO after I moved to the "tools"-team. I mainly checked the subject line so in individual instances you might not agree to take it over completely into QSF-u. Feel free to discuss with me or reassign to me or someone else in this case. Thanks.
- Target version changed from Milestone 25 to Milestone 26
- Status changed from Blocked to Workable
- Assignee deleted (
mgriessmeier)
- Target version changed from Milestone 26 to Milestone 27
grooming, might be able to unify into one ticket about mistyping
- Blocked by deleted (action #46508: [qe-core][functional] Ensure to use a clean "extra" console for keymap_or_locale and / or do not try to login (at least on local backends))
- Status changed from Workable to Rejected
- Assignee set to mgriessmeier
Let's reject in favor of #43889
Also available in: Atom
PDF