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

failed already at https://openqa.opensuse.org/tests/2235822#step/updates_packagekit_gpk/24
and
http://10.162.30.85/tests/4622#step/check_system_is_updated/12
I don't think this will work and stay stable for long time: 64bit-2G machine for such complete and updated installation, with testing of application like chromium.

I checked this and found in Jobgroup of DVD-Updates:

x86_64:
    opensuse-15.3-DVD-Updates-x86_64:
    - textmode:
        machine: 64bit
    - gnome:
        machine: uefi
        settings:
          QEMUVGA: cirrus
    - gnome:
        machine: 64bit-2G
        settings:
          QEMUVGA: cirrus

Same tests but on different machines and this is clearly a performance issue . 64bit-2G is so instable and won't schedule such heavy installation/update tests on it. I can exclude chromium for a observation. If other test modules are also love to fail, then I can un-schedule it.

https://openqa.opensuse.org/t2243182

try to verify this issue directly on O3 because my local openqa server has problem with installation (repo issue, network issue).

according to my tests (more than 100 test runs), there is not a problem to chromium test module, but to performance of worker:

• no issue with qemuram, but found evidence for network issue: 10.162.30.85/tests/4923#step/updates_packagekit_gpl/17 and
• my assumption for poor cpu power, because there is no specific recording for cpu performance in logs, which cannot be determined at all.
• call trace has been displayed from POST_FAIL_HOOKS, not the problem causes failure Normal successful test run on my slow machine takes about 1 hour 50 minutes. So I don't see an issue with MAX_JOB_TIME=14400

zluo wrote:

according to my tests (more than 100 test runs), there is not a problem to chromium test module, but to performance of worker:

so what do you suggest to do about such "performance of worker"-problem?

@okurz I would suggest to rapidly reduce the number of workers of 64G-2GB machine. Single worker on my test machine works fine and can prevent this kind of issue.

zluo wrote:

@okurz I would suggest to rapidly reduce the number of workers of 64G-2GB machine. Single worker on my test machine works fine and can prevent this kind of issue.

which worker host are you talking about here please? Yes, likely personal workstations have lower load anyway, so production tests need to accomodate for that within the test design.