QA (public) » openQA Project (public) » openQA Tests (public)

We should solve it for GMC, hence increasing the priority.

Alright, so that's the problem of the schedule. I've retriggered it with YAML_SCHEDULE unset: https://openqa.suse.de/t2925810 to make it not that urgent, but we need to address this issue, as yaml schedule for staging didn't work for all.

Now I need to crosscheck if all of them worked fine, as there is an issue that we execute less tests in some case in comparison to main.pm scheduling and list them here.

I was checking with oorlov that, and the conclusion was that we should keeps the same schedule for staging but for our groups all those tests seems the same than the one that are performed after default, so we decided to excluded (which in some cases with hyperv afteward I was not so sure if was the right choice) but the thing is that some teams are using the wrong test suite to schedule banch of stuff after installing instead of default, but when we separate yaml there is no problem about to still keep it or not, it is just for us to decide at least in our group.

Fix migrated scenarios to yaml: svirt-hyperv and xen-pv -> Merged

All setup done! huge work of configuration, but I hope it worths, now staging is frozen with staging test suites and we also have our test suites for the jobs that are in staging. Still there is a couple of things to do to make totally plane (without conditions) the schedules.

PR: Fix yaml migration: s390x differences -> Merged