Project

General

Profile

Actions
Copy link

action #45833

closed

[jeos] fix console/cups tests for jeos

Added by thehejik over 6 years ago. Updated 6 months ago.

Status:
Resolved
Priority:
High
Assignee:
thehejik
Target version:
-
Start date:
2019-01-08
Due date:
% Done:

100%

Estimated time:
Tags:
MinimalVM

Description

Both tests (cups and mutt) are failing on JeOS SLE15-SP1.

So far I can see two problems:

  • wget is not available in JeOS (we can install it or use curl instead which is preinstalled everywhere)
  • select_serial_terminal() requires - use base "opensusebasetest" (instead of consoletest)

Its failing here https://openqa.suse.de/tests/2358617

Actions
Copy link
 #1

Updated by ccret over 6 years ago

I am already working on updating the mutt test. https://progress.opensuse.org/issues/45788
I will take a look at the cups one unless someone is already working on that.

Actions
Copy link
 #2

Updated by thehejik over 6 years ago

  • Subject changed from fix console/cups and console/mutt tests for jeos to [jeos] fix console/cups tests for jeos
Actions
Copy link
 #3

Updated by thehejik over 6 years ago

  • Status changed from New to In Progress
  • Assignee changed from jbaier_cz to thehejik
Actions
Copy link
 #4

Updated by zluo over 6 years ago

we have problem with mutt on osd:

http://openqa.suse.de/tests/2361581#step/mutt/24

It seems there is a problem with needle "mutt-message-list".

Actions
Copy link
 #5

Updated by ccret over 6 years ago

@zluo From what I can tell it's not about the needle. The message is not displayed in that inbox even tough it looks fine in the postfix log. My guess it that it didn't get a chance to refresh the inbox since the same test passes over here https://openqa.suse.de/tests/2361563#.

Actions
Copy link
 #7

Updated by thehejik over 6 years ago

Problem solved on x86_64, see https://openqa.suse.de/tests/2363777#step/cups/1

but on rpi there is still a problem with unavailable serial console. I have changed test-suite definition for all jeos-RPi*tests by adding following entries:

EXTRABOOTPARAM=console=ttyAMA0,115200
IPXE=0

But now keyboard selection is failing in my "qemu-emu-aarch64" env for some strange reason - it uses ee-dvorak http://dhcp105.suse.cz/tests/1218#step/firstrun/6

Let see what will happen on OSD

Actions
Copy link
 #8

Updated by okurz over 6 years ago

  • Priority changed from Normal to High

This ticket is used in currently failing openQA tests as label. Is it ok if I set the prio to "High" for you?

Actions
Copy link
 #9

Updated by thehejik over 6 years ago

  • Status changed from In Progress to Resolved
  • % Done changed from 0 to 100

The test is now working - I "fixed" that by defining VIRTIO_CONSOLE=0 in the testsuite "jeos-extratest-RPi". For x86_64 there is no issue with that.

Working test https://openqa.suse.de/tests/2377293#step/cups/1 (and also mutt https://openqa.suse.de/tests/2377293#step/mutt/1)

Basically now we are not using serial console login in "jeos-extratest-RPi" test.

Actions
Copy link
 #10

Updated by okurz over 6 years ago

I understood that VIRTIO_CONSOLE was meant to be set depending on the qemu version if it supports virtio or not. I really do not understand why a testsuite should behave different.

Actions
Copy link
 #11

Updated by okurz about 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: extra_tests_in_textmode@svirt-xen-hvm
https://openqa.suse.de/tests/2407680

Actions
Copy link
 #12

Updated by jlausuch about 4 years ago

  • Project changed from openQA Tests (public) to 208
  • Category deleted (Bugs in existing tests)
Actions
Copy link
 #13

Updated by ph03nix 6 months ago

  • Tags set to MinimalVM
Actions
Copy link
 #14

Updated by ph03nix 6 months ago

  • Project changed from 208 to Containers and images
Actions
Copy link

Also available in: Atom PDF