Project

General

Profile

action #33976

[sle][functional][u][ppc64le][fast] test fails in install_test_suite - key input problem with zypper command

Added by zluo about 2 years ago. Updated about 2 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Bugs in existing tests
Start date:
2018-03-28
Due date:
2018-05-08
% Done:

0%

Estimated time:
Difficulty:
Duration: 30

Description

zzypper found in console screen, so test_suite cannot be installed.

Observation

openQA test in scenario sle-15-Installer-DVD-ppc64le-sched_stress@ppc64le fails in
install_test_suite

Reproducible

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

Expected result

Last good: 533.2 (or more recent)

Further details

Always latest result in this scenario: latest

History

#1 Updated by okurz about 2 years ago

  • Subject changed from [sle][functional] test fails in install_test_suite - key input problem with zypper command to [sle][functional][u][ppc64le][fast] test fails in install_test_suite - key input problem with zypper command
  • Due date set to 2018-04-10
  • Status changed from New to Workable
  • Priority changed from Normal to Urgent
  • Target version set to Milestone 15

If we are really having troubles with typing again on ppc64le then we should not take this lightly. All our current ppc64le are considered to be stable. This needs to be handled urgently. Please see which worker was used and consult QA tools team.

#2 Updated by dheidler about 2 years ago

  • Status changed from Workable to In Progress

Worker QA-Power8-4-kvm:4 (https://openqa.suse.de/admin/workers/947)

#3 Updated by dheidler about 2 years ago

  • Assignee set to dheidler

#5 Updated by dheidler about 2 years ago

There is code to cancel the test, if the key event queue fills up.
See backend/qemu.pm:

for my $line (split(/\n/, $buffer)) {
    bmwqemu::diag "QEMU: $line";
    die "QEMU: Shutting down the job" if $line =~ m/key event queue full/;
}

But it doesn't seem as if it would have been executed on the affected test.

#6 Updated by dheidler about 2 years ago

  • Status changed from In Progress to Feedback
  • Priority changed from Urgent to Normal

Generally reading the Bugzilla ticket it seems that the workaround of setting qemu argument -smp 1,threads=1 improves the test stability,
but it still happens sometimes.
Looking at the previous results the tests look pretty stable though.

Keeping this on feedback as there is nothing we can do about this at the moment (there is no real progress in bugzilla and there is no real input from IBM, yet).

#7 Updated by mgriessmeier about 2 years ago

  • Due date changed from 2018-04-10 to 2018-04-24

#8 Updated by mgriessmeier about 2 years ago

  • Due date changed from 2018-04-24 to 2018-05-08
  • Target version changed from Milestone 15 to Milestone 16

#9 Updated by okurz about 2 years ago

  • Status changed from Feedback to Resolved

Looking at https://openqa.suse.de/tests/1655297 I can see that at least 10 jobs in a row succeeded so it's not a big issue in general. With the current workarounds in place I guess we are fine for the time being.

Also available in: Atom PDF