QA » openQA Project » openQA Tests

This sporadic issue is seen on aarch64 platform in past few builds.
We may need wait for more time to catch the right needle.

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

the general problem is poor performance, with 1024 MB and 1 core.
So try to set timeout where is needed: needles match.

this is weird, to compare with this on osd:
with code change but not related:
https://openqa.suse.de/tests/10698443#step/libqt5_qtbase/56 shows that failed at assert_script_run './libqt5-qtbase' on x86_64

without changes on osd:
http://10.161.8.50/tests/7#step/libqt5_qtbase/56 failed as well at same place.

Now I tried clone job again on osd without code change:
https://openqa.suse.de/tests/10698499 succesful again!

https://openqa.suse.de/tests/10701696#step/libqt5_qtbase/13 shows even already failed to start xterm.

this is clearly a serve performance issue on aarch64.

https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/16612 updated, also take care of tumbleweed

openqa_review wrote:

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_gnome_sdk
https://openqa.suse.de/tests/10718625#step/libqt5_qtbase/1

To prevent further reminder comments one of the following options should be followed:

1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
2. The openQA job group is moved to "Released" or "EOL" (End-of-Life)
3. The bugref in the openQA scenario is removed or replaced, e.g. label:wontfix:boo1234

Expect the next reminder at the earliest in 28 days if nothing changes in this ticket.

this is a performance issue which happens very rarely. I see that following 3 test runs are successful.

I change a little bit for testsuite on OSD:
extra_tests_gnome_sdk
give 1024 more qemuram and 2 more qemucpus

QEMUCPUS=4
QEMURAM=3072

https://openqa.suse.de/tests/10940821 looks good, but still need more successful test runs from now.

https://openqa.suse.de/tests/11014888#next_previous should be okay for now.