Project

General

Profile

Actions

action #46490

closed

[functional][u][sporadic] test fails in execute_test_run: char gets double-typed

Added by dheidler almost 6 years ago. Updated almost 6 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Bugs in existing tests
Target version:
SUSE QA (private) - Milestone 25
Start date:
2019-01-22
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Observation

openQA test in scenario sle-15-SP1-Installer-DVD-ppc64le-qa_userspace_findutils@ppc64le fails in
execute_test_run

Reproducible

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

Expected result

Last good: 143.1 (or more recent)

Further details

Always latest result in this scenario: latest

Sometimes when openQA types if the SUT gets iif which makes the test fail.


Related issues 2 (1 open1 closed)

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

Actions
Blocked by openQA Tests (public) - action #44138: [functional][u][userspace] tests in QAM which seem to be the equivalent look so much easier to review, crosscheckResolvedokurz2018-11-21

Actions
Actions #1

Updated by okurz almost 6 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: qa_userspace_findutils
https://openqa.suse.de/tests/2458971

Actions #2

Updated by okurz almost 6 years ago

  • Target version set to Milestone 24
Actions #3

Updated by okurz almost 6 years ago

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

Updated by okurz almost 6 years ago

  • Blocked by action #44138: [functional][u][userspace] tests in QAM which seem to be the equivalent look so much easier to review, crosscheck added
Actions #5

Updated by okurz almost 6 years ago

  • Status changed from New to Blocked
  • Assignee set to okurz
  • Target version changed from Milestone 24 to Milestone 25
Actions #6

Updated by okurz almost 6 years ago

  • Status changed from Blocked to Resolved

With #44138 we execute a completely different code path so we should not invest time in this ticket as is. However as we use VIRTIO_CONSOLE=1 in the test scenarios the original problem will most likely not appear.

Actions

Also available in: Atom PDF