Remove yast2_i from QSF-U group #10317
Conversation
schedule/functional/minimal_x.yaml
Outdated
| - console/zypper_lr | ||
| - console/zypper_ref | ||
| - console/ncurses | ||
| - console/yast2_lan |
There was a problem hiding this comment.
I guess yast2_lan can also be removed
There was a problem hiding this comment.
This one you can remove for sure, as of now we had to add this module to EXCLUDE_MODULES in https://gitlab.suse.de/qsf-u/qa-sle-functional-userspace/-/blob/master/functional_sle15_jobgroup.yaml#L15 because main.pm uses it and we didn't want to change scope of QAM tests.
There was a problem hiding this comment.
This one you can remove for sure, as of now we had to add this module to EXCLUDE_MODULES in https://gitlab.suse.de/qsf-u/qa-sle-functional-userspace/-/blob/master/functional_sle15_jobgroup.yaml#L15 because main.pm uses it and we didn't want to change scope of QAM tests.
|
Now I wonder if keyboard_layout_gdm should also be scheduled (and reworked so it covers both: minimalx and gdm) |
There was a problem hiding this comment.
We have https://progress.opensuse.org/issues/66209
In case you are in a hurry, go ahead and disable all of those.
What about yast2_booloader? |
https://openqa.suse.de/tests/overview?arch=&machine=&modules=yast2_booloader&distri=sle&version=15-SP2&build=195.1&groupid=110# doesn't show any test suite running it. So what's about yast2_bootloader? |
I spotted a typo |
Ah, ok. I will create another ticket, sure |
|
Ready to be merged |
_EXIT_AFTER_SCHEDULE=1)