action #95914
closed[y][qe-yast] test fails in yast2_storage_ng, likely test regression
0%
Description
Observation¶
openQA test in scenario sle-15-SP2-Server-DVD-Updates-x86_64-mau-extratests-yast2ui@64bit fails in
yast2_storage_ng
Test suite description¶
Run YaST2 GUI tests
Reproducible¶
Fails since Build 20210722-1, reproducible in https://openqa.suse.de/tests/latest?arch=x86_64&distri=sle&flavor=Server-DVD-Updates&machine=64bit&test=mau-extratests-yast2ui&version=15-SP2
Expected result¶
Last good: 20210721-1
Problem¶
According to https://openqa.suse.de/tests/6532370#comment-364885 a likely test regression
git log between "last good" and "first bad":
test_log
0860cca9c Revert is_tumbleweed from is_storage_ng
8b097ebee Use serial console on Maintenance install MR
d344d19ba Return updated path when using AutoYaST templates
766e9677e Extend AutoYaST file(s) preparation for Rules and Classes
5ab01c7b4 Fix the old/new autoyast xml element on 15 SP3
13001ccef Yaml schedule for create-QAM-Installtest-SLE[SD]-image test
ee5656645 Revert "Extend AutoYaST file(s) preparation for Rules and Classes"
6afa01d14 SLE Micro: add migration test from 5.0 to 5.1
3d5b13472 Increase login timeout in gnome
764d88992 Schedule vsftpd in s390x maintenance runs
ce78d29c9 Add schedule for future testing of AutoYaST rules and classes.
3e2f076f1 Add documentation for AutoYaST when using rules and classes
5e8086442 Changes in ay prepare_profile
bbe6f4024 Add AutoYaST lib functionality to handle rules and classes
0b58f877e clamav: Increase timeout on clamd freshclam stop
2e83076ea thunderbird: Wait after pressing alt-n to avoid typo
c174f636c systemtap: Increase timeout on Hello world example
b861887b8 Add password possibility for ssh access with s390x on Tumbleweed (poo#93949)
0db8ea575 Remove ctdb module from rolling_upgrade test in QAM
cff512c60 lib/x11utils.pm: Handle gnome-activities in ensure_unlocked_desktop
dc018adf1 Soft-fail vsftpd module for s390x runs
9ddc2ded0 Add data for AutoYaST rule-based scenario
Further details¶
Always latest result in this scenario: latest
Impact¶
Reproducible problem in aggregate maintenance tests in this test suite
Updated by dzedro over 2 years ago
@okurz please stop blindly creating issues on maintenance failures!
This did just hide possible regression.
Updated by okurz over 2 years ago
dzedro wrote:
@okurz please stop blindly creating issues on maintenance failures!
I am merely trying to follow the procedures to the best of my knowledge. I am not creating issues "blindly". Also a ticket in a test regression tracker does not mean that the failure can be ignored. No one is guaranteed to always identify "product vs. test regression" on the first look.
This did just hide possible regression.
good that you found this.