QA (public) » openQA Project (public) » openQA Tests (public) » qe-yam

Manually test the case on a vm: install SLES15SP5 build70.1 with VIDEOMODE text mode configuring machine with 1 cpu and 2 GB of RAM, the bug is not fixed yet.

Tested it again with today's new build72.1, the bug is fixed, will add test suites.

Submit a PR to add case's schedule yaml file, the cases in staging job group are triggered with setting
YAML_SCHEDULE=schedule/staging/%TEST%@%MACHINE%-staging.yaml, so I add schedule/staging/textmode_install@64bit-staging.yaml to openqa source code.
PR: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/16410

It's not related with build, we can all focus on the Build and leave aside those other tasks, move them to the bottom of our backlog and/or resolve the parts already done. (jrivera: it is related, it is related with a bug that should have been found in staging)

PR merged, could you please setup the test suite in staging, but commented with some reference to the bug, I mean, we cannot run it, because the bug is not solved, so we can activate the scenario later (there is not control version).
btw we need to avoid to run that job even in another job group (development for example), because it is connected with obs, blocking staging, see:
https://suse.slack.com/archives/C02CANHLANP/p1677239751899489
Once you have done that, let's create a progress ticket for us to activate the scenario with the configuration that is required in job group. After we can resolve this one.

JERiveraMoya wrote:

PR merged, could you please setup the test suite in staging, but commented with some reference to the bug, I mean, we cannot run it, because the bug is not solved, so we can activate the scenario later (there is not control version).

Thanks, I think the bug is already fixed since build72.1, see the test runs in openqa:
build72.1: https://openqa.suse.de/tests/10514323 (pass)
build70.1: https://openqa.suse.de/tests/10514322#step/setup_libyui/1 (still fail on the build before the 72.1)
And here is the case in bug description which is also pass on build72.1:
https://openqa.suse.de/tests/10490513

btw we need to avoid to run that job even in another job group (development for example), because it is connected with obs, blocking staging, see:
https://suse.slack.com/archives/C02CANHLANP/p1677239751899489

OK, I get it, I remove it from the dev group, and removed the triggered cases.

Once you have done that, let's create a progress ticket for us to activate the scenario with the configuration that is required in job group. After we can resolve this one.

If the bug is already fixed, then I can add the testsuite to staging and activate it, right?

yes, let's do it, sorry, I got confused by the comment in slack ...