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

Thanks for the notice. This must definitely some error on my side, not sure why at the moment. Although I don't work with SP4 I will check that issue later. So far it didn't happen on SP2/SP3.

hm, sure it could be something 12SP4 specific problem but I doubt this is true. I consider it more likely that aarch64 is the culprit having different timing behaviour. I have the feeling that the many wait_still_screen 1 in the test module are not the most robust choice.

I agree that 'wait_still_screen' seems to be overused (it was my 1st contact with openQA that time). My current idea is to replace each step with assert screen (to avoid possible timing issues). What do you think?

The problem is that I don't have aarch64 worker available for my private openQA instance. Do you know who could lend me aarch64 for short time?

pcervinka wrote:

I agree that 'wait_still_screen' seems to be overused (it was my 1st contact with openQA that time). My current idea is to replace each step with assert screen (to avoid possible timing issues). What do you think?

Well, at best a console based test does not need to rely on any screen checks except when you really want to check the rendering of a UI. I suggest to use either wait_serial in combination with assert_script_run/script_run calls or do the actual test using something like expect.

The problem is that I don't have aarch64 worker available for my private openQA instance. Do you know who could lend me aarch64 for short time?

I guess "aarch64" is only triggering failures because it is slower. That should not mean you need to test on aarch64. For the purpose of simulating a slow aarch64 instance you can actually use qemu to emulate the architecture. If you really want to test on aarch64 then I suggest to lend a machine on orthos

I remember now, why is used wait_stil_screen so much. There are several options entered in one command in "question and answer" mode during key generation.

Ok, I will focus only on that particular line 73 with validat_screen_output.

Happened also on SLE12 x86_64 https://openqa.suse.de/tests/1548776#step/gpg/28

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

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: extra_tests_in_textmode
https://openqa.suse.de/tests/1535915

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: extra_tests_in_textmode
https://openqa.suse.de/tests/1588098