action #55445
closed[functional][u] On OSD get rid of workaround QEMUVGA=cirrus in machines
0%
Description
Motivation¶
See ticket #53339 . We have already done the corresponding change on openqa.opensuse.org
Acceptance criteria¶
- AC1: default machines on https://openqa.suse.de/admin/machines do not mention
QEMUVGA=cirrusanymore
Suggestions¶
- A disk image created with CIRRUS cannot be booted properly with the default (STD)
- Upgrade scenarios still need CIRRUS, unless we recreate the images with STD.
- Extra tests generate their own images, so they can be changed.
Tasks¶
- Crate new machines 64bit_cirrus and uefi_cirrus
- Remove QEMUVGA setting from 64bit* and uefi*, aarch64*, ppc64le*, zKVM* machines
Updated by okurz over 5 years ago
- Copied from action #53339: [opensuse] test fails in swing due to incorrect rendering on 16bpp framebuffers added
Updated by okurz over 5 years ago
- Subject changed from [functional][u] check if QEMUVGA=cirrus can be removed from default, remove from machines afterwards to [functional][u] On OSD get rid of workaround QEMUVGA=cirrus in machines
Updated by SLindoMansilla about 5 years ago
- Priority changed from Normal to High
Updated by SLindoMansilla about 5 years ago
- Description updated (diff)
- Start date changed from 2019-06-19 to 2019-10-28
This ticket should be workable after SLE12-SP5 GMCC1 and SLE15-SP2 Alpha5
Updated by okurz about 5 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: toolkits
https://openqa.suse.de/tests/3527493
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
Updated by szarate about 5 years ago
@dheidler how is this related to https://openqa.suse.de/tests/3571133#step/swing/12 ?
Updated by okurz about 5 years ago
#53339 was the original ticket about the same test scenario on o3 that motivated us to finally step away from cirrus. So probably the move away from the cirrus workaround will fix the swing test failure.
Updated by dheidler about 5 years ago
@szarate: Swing has problems rendering when ran unter cirrus.
But it works with std.
Updated by dheidler about 5 years ago
- Status changed from Workable to In Progress
Updated by dheidler about 5 years ago
Updated YAML of SLE15 Migration jobgroup
@@ -9,7 +9,7 @@
machine: s390x-kvm-sle15
priority: 50
x86_64:
- machine: 64bit
- machine: 64bit_cirrus priority: 50 products: sle-15-SP2-Migration-from-SLE11-SP4-to-SLE15-SP2-x86_64:
Updated by dheidler about 5 years ago
- Status changed from In Progress to Feedback
Changes to machines done - let's see what will happen on next build.
Updated by okurz about 5 years ago
Please keep in mind that the final goal needs to be to not use "cirrus" anywhere anymore especially as now even more recent versions of qemu, e.g. on Tumbleweed, do not even support cirrus properly anymore.
Updated by dheidler about 5 years ago
This fixed at least the swing test: https://openqa.suse.de/tests/3613873
Updated by dzedro about 5 years ago
- Related to action #60257: [functional][u][mistyping] random typing issues on wayland added