action #119134
closed[qem][qe-core]test fails in clone, yast clone_system seems hang
0%
Description
Observation¶
openQA test in scenario sle-15-SP4-Server-DVD-Updates-aarch64-qam-gnome@aarch64-virtio fails in
clone
Test suite description¶
Testsuite maintained at https://gitlab.suse.de/qa-maintenance/qam-openqa-yml.
Reproducible¶
Fails since (at least) Build 20221019-1
Expected result¶
Last good: 20221018-1 (or more recent)
Further details¶
Always latest result in this scenario: latest
Updated by rfan1 over 1 year ago
It has failed several time from 10/19, and seems 'yast clone_system' command hang there:
https://10.160.0.207/tests/9775384#step/clone/11
We may increase the memory size and re-run, or it might be a product bug.
Updated by zluo over 1 year ago
- Status changed from New to In Progress
- Assignee set to zluo
take over and check
Updated by zluo over 1 year ago
https://openqa.suse.de/tests/9777085
the worker is extremly slow, need to find a proper value for timeout.
[2022-10-21T16:02:00.168283+02:00] [debug] <<< testapi::wait_serial(quiet=undef, regexp="yast2-clone_system-status-0", no_regex=0, buffer_size=undef, timeout=1400, expect_not_found=0, record_output=undef)
[2022-10-21T16:17:15.744302+02:00] [debug] >>> testapi::wait_serial: yast2-clone_system-status-0: ok
it took longer than 900 seconds :)
Updated by zluo over 1 year ago
Updated by rfan1 over 1 year ago
- Related to action #115079: [qe-core][qem&functional] Many test failures due to low performance on arm workers added