action #166988
closed[qe-core] test fails in yast2_i - exclude yast2_* modules from maintenance qam-minimal-full
0%
Description
Observation¶
Before excluding these modules from the schedule, we need to verify if QE-Yam is running these or what is their status (are they supported for a given product?)
openQA test in scenario sle-15-SP3-Server-DVD-Incidents-Minimal-aarch64-qam-minimal-full@aarch64 fails in
yast2_i
Test suite description¶
Testsuite maintained at https://gitlab.suse.de/qa-maintenance/qam-openqa-yml. minimal = base pattern, minimal (enhanced base) pattern are additional convenience paclkages
Reproducible¶
Fails since (at least) Build :35625:glibc
Expected result¶
Last good: :35604:dtb-aarch64 (or more recent)
Further details¶
Always latest result in this scenario: latest
Updated by cvidot about 1 month ago
- Status changed from Workable to In Progress
- Assignee set to cvidot
Updated by cvidot about 1 month ago
Updated by dzedro about 1 month ago
Firs look on the failed tests appeared as needle mismatch, if just new needle is required I would keep the tests.
Updated by szarate about 1 month ago
dzedro wrote in #note-3:
Firs look on the failed tests appeared as needle mismatch, if just new needle is required I would keep the tests.
I'm more into dropping them as they fail once every couple weeks, but see also https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/20238#issuecomment-2374116062
Up to you @dzedro/@cvidot
Updated by cvidot 30 days ago
I removed yast2_i and yast2_bootloader from the schedule in my PR as per szarate's comment.
@dzedro If you have any objection and you still think we should keep them, let me know. I don't have enough experience with the modules to have a say in the matter.
Updated by szarate 27 days ago
created https://progress.opensuse.org/issues/167620 after a small convo on: https://suse.slack.com/archives/C02CLB2LB7Z/p1727688952788809?thread_ts=1726818239.399269&cid=C02CLB2LB7Z:
I’ll be dropping progressively yast_* modules as they start failing, and will add a ticket for you and Heiko to decide what to do in such case, as these would then end up being orphaned and we’ll end up losing test coverage.
So we can move this forward
Updated by dzedro 26 days ago
cvidot wrote in #note-5:
I removed
yast2_iandyast2_bootloaderfrom the schedule in my PR as per szarate's comment.@dzedro If you have any objection and you still think we should keep them, let me know. I don't have enough experience with the modules to have a say in the matter.
I don't mind.