action #55448
closed[opensuse] cleanup cirrus/std/qxl ob o3
0%
Description
Motivation¶
See #53339
Acceptance criteria¶
- AC1: All jobs against "64bit_std" are removed from Development Tumbleweed
- AC2: All machine definitions for "64bit_std" are removed from o3
- AC3: All jobs against "64bit_qxl" are removed (or moved into product validation job group)
Updated by okurz over 4 years ago
- Copied from action #53339: [opensuse] test fails in swing due to incorrect rendering on 16bpp framebuffers added
Updated by okurz over 4 years ago
- Subject changed from [opensuse] test fails in swing due to incorrect rendering on 16bpp framebuffers to [opensuse] cleanup cirrus/std/qxl ob o3
asked dimstar and fvogt in #opensuse-factory and they are ok with my approach. Removed the scenarios @64bit_std "create_hdd_gnome", "create_hdd_kde", "create_hdd_textmode", "create_hdd_xfce", "desktopapps-gnome", "extra_tests_in_textmode", "extra_tests_on_gnome", "extra_tests_on_kde", "extra_tests_on_xfce", "kde", "minimalx", "qemu", "textmode", "toolkits", "update_13.1-gnome", "update_Leap_15.1_gnome", "update_Leap_42.3_kde", "virtualization", "yast2_gui", "yast2_ncurses", "zdup-Leap-42.3-kde", "gnome-live", "kde-live_installation" after checking that their "64bit" counterparts within the product validation job group are fine. Deleted the machine "64bit_std" as well
Updated by okurz over 4 years ago
- Status changed from Feedback to Resolved
Moved the single remaining "gnome@64bit_qxl" into the product validation job group. It's not passed but seems to show problems that are common and shared so I hope we are ok with tracking this there.