QA » openQA Project » openQA Tests

queried in yast channel:

the case in https://openqa.opensuse.org/tests/858922/modules/yast2_i/steps/8 is about spice-vdagent due to we're running test on VM,
maxlin: yes, looks like related, that package supplements "modalias(xorg-x11-server:virtio:d00000003v*)" so I guess that matches the VM environment
maxlin: from y2log: y2packager/system_packages.rb:41 Preselecting system packages: ["spice-vdagent"]
maxlin: so yes, that's that new preselecting driver packages feature

the behavior has documented at https://github.com/yast/yast-packager/wiki/Selecting-the-Driver-Packages

It might influence us for SLE15SP1 as https://build.suse.de/request/show/184671 is not yet accepted but nearly so however I still suggest to get TW covered first according to our best practices.

SLE staging tests currently fail on a dependency conflict about busybox-static. As soon as that is fixed we might hit the problem in the yast2_i module in staging tests however could be that we do not see it there when staging tests do not add any additional repos.

In some cases more packages are preselected than just spice-vdagent, as here : https://openqa.opensuse.org/tests/860450#step/yast2_i/8 .

Please see what ccret did with https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/6873

Wait, it was DimStar messing around here :) -> https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/6899

We have get qt test failing as we got a package to be installed, which is not expected. https://openqa.opensuse.org/tests/868600#step/yast2_software_management/14
Should we fix within this ticket or schedule it separately along with refactoring?

hm, depends on time criticality. Whatever is necessary to fix currently failing tests first and other improvements later. Sorry, I don't understood the full picture here.

riafarov wrote:

We have get qt test failing as we got a package to be installed, which is not expected. https://openqa.opensuse.org/tests/868600#step/yast2_software_management/14
Should we fix within this ticket or schedule it separately along with refactoring?

I can easily do it as a part of this ticket, the package was installed successfully, but we do not really close the window.

Please be aware that currently 12 scenarios in openSUSE Tumbleweed are failing in "yast2_i" module: https://openqa.opensuse.org/tests/overview?arch=&modules=&distri=opensuse&groupid=1&version=Tumbleweed&failed_modules=yast2_i this can be adressed in this ticket or #48512 as well

PR2:

https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/6968

okurz wrote:

Please be aware that currently 12 scenarios in openSUSE Tumbleweed are failing in "yast2_i" module: https://openqa.opensuse.org/tests/overview?arch=&modules=&distri=opensuse&groupid=1&version=Tumbleweed&failed_modules=yast2_i this can be adressed in this ticket or #48512 as well

Different issue, I would prefer to leave it for https://progress.opensuse.org/issues/48512