Project

General

Profile

action #19396

[opensuse][ppc64] test fails in welcome with "character artifacts" -> invalid bug suggests "console=hvc"

Added by okurz over 5 years ago. Updated about 1 year ago.

Status:
In Progress
Priority:
Low
Assignee:
-
Category:
Bugs in existing tests
Target version:
-
Start date:
2017-05-26
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Observation

openQA test in scenario opensuse-Tumbleweed-DVD-ppc64le-textmode@ppc64le fails in
welcome
showing character artifacts.

Reproducible

Fails since (at least) Build 20170505

Expected result

Last good: 20170504 (or more recent)

https://bugzilla.suse.com/show_bug.cgi?id=1025622 is a bug used as label in other related jobs. It suggests to add "console=hvc". Probably this is what we should do.

Further details

Always latest result in this scenario: latest

History

#1 Updated by okurz over 5 years ago

  • Description updated (diff)

#2 Updated by michel_mno over 5 years ago

I do not understand what detailed changes need to be done to implement the suggestion to add "console=hvc"

In the mean time I added two workaround needles used in (1)

(1) https://openqa.opensuse.org/tests/410374

#3 Updated by okurz over 5 years ago

  • Status changed from New to In Progress

Adding "console=hvc" would mean within the test code as part of os-autoinst-distri-opensuse one would need to find all locations where "console=…" is set in the bootloader parameters for either the installation system (linuxrc) only or also the installed system (grub command line). In this case for ppc64(le) I assume it's the methods bootmenu_default_params and specific_bootmenu_params in lib/bootloader_setup.pm for the ppc64le (and/or ppc64) branch.

open questions:

  • what is the exact call path now for ppc64le?
  • does it differ for ppc64?
  • is the console already set at all?

#4 Updated by okurz over 5 years ago

see https://github.com/os-autoinst/os-autoinst-needles-opensuse/pull/212 for making the existing soft-fails reference this progress issue instead of the bug which is closed as invalid.

#5 Updated by okurz about 1 year ago

  • Priority changed from Normal to Low

This ticket was set to "Normal" priority but was not updated within 730 days which is 2 times the period of the SLO for "Normal" tickets (365 days) as described on https://progress.opensuse.org/projects/openqatests/wiki/Wiki#SLOs-service-level-objectives . The ticket will be set to the next lower priority of "Low".

Also available in: Atom PDF