action #125873
closed
[qe-core][functional]test fails in libqt5_qtbase, sporadic issue
Added by rfan1 over 1 year ago.
Updated over 1 year ago.
Category:
Bugs in existing tests
Description
Observation¶
openQA test in scenario sle-15-SP5-Online-aarch64-extra_tests_gnome_sdk@aarch64 fails in
libqt5_qtbase
Test suite description¶
Maintainer: jrauch. Extra tests about software in SDK module
Reproducible¶
Fails since (at least) Build 79.1 (current job)
Expected result¶
Last good: 77.1 (or more recent)
Further details¶
Always latest result in this scenario: latest
This sporadic issue is seen on aarch64 platform in past few builds.
We may need wait for more time to catch the right needle.
- Status changed from New to In Progress
- Assignee set to zluo
the general problem is poor performance, with 1024 MB and 1 core.
So try to set timeout where is needed: needles match.
- Status changed from In Progress to Resolved
- Status changed from Resolved to Feedback
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:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- 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.
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:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- 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
- Status changed from Feedback to Resolved
Also available in: Atom
PDF