Project

General

Profile

Actions

action #158458

closed

Increase RAM for test cases "yast-mru-install-minimal-with-addons" in "YaST Maintenance Updates", aarch64 and x86_64

Added by lmanfredi about 1 month ago. Updated 24 days ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
2024-04-03
Due date:
% Done:

0%

Estimated time:

Description

Motivation

There are some failed jobs in job group 421 YaST Maintenance Updates due the timeout in test module installation/grub_test.pm

After increase RAM to 4G for cloned jobs, it works fine

The ARCHs are:

  • aarch64
  • x86_64

The tests:

  • yast-mru-install-minimal-with-addons / Version: 15-SP2 / Flavor: Server-DVD-Updates
  • yast-mru-install-minimal-with-addons / Version: 15-SP3 / Flavor: Server-DVD-Updates

Repo file:

Todo

Increase QEMURAM to 4G: QEMURAM="4096"

Acceptance criteria

AC1: Increase QEMURAM

Actions #1

Updated by JERiveraMoya about 1 month ago

you need more than one run to probe that the RAM make it pass, it could be any other temporary thingy. For example today all the failures are gone.
I would recommend next time statistical analysis, at least 10 for example.
On the other hand with a gnome most likely we need that amount of RAM by default.

Actions #3

Updated by pcervinka about 1 month ago

We notice similar issue https://openqa.suse.de/tests/13960449#step/grub_test/2 and QEMURAM=4096 didn't help.

Actions #4

Updated by leli about 1 month ago · Edited

It seems issue for INSTALLER_SELF_UPDATE, if set it as null then passed: http://openqa.suse.de/tests/13960826#

Actions #5

Updated by JERiveraMoya about 1 month ago

too many self-updates can eat the memory but he problem is normally seen on booting.
@leli could you apply the statistical analysis I mentioned above and if the self_update is what really makes the difference, communicate it in the proper Slack channel for maintainers of those channels?

Actions #6

Updated by pstivanin about 1 month ago

we are also facing the same issue. Weirdly enough, the desktop installation with 2GB passes, while the minimal installation with 4GB fails.

Actions #7

Updated by leli about 1 month ago · Edited

JERiveraMoya wrote in #note-5:

too many self-updates can eat the memory but he problem is normally seen on booting.
@leli could you apply the statistical analysis I mentioned above and if the self_update is what really makes the difference, communicate it in the proper Slack channel for maintainers of those channels?

Asked this in team-lsg-qe-openqa-review channel: https://suse.slack.com/archives/C02D16TCP99/p1712560469995439

Actions #8

Updated by pcervinka about 1 month ago

We had another strange failure in installation https://openqa.suse.de/tests/13963317#step/await_install/77 and looks that clearing INSTALLER_SELF_UPDATE helped as well https://openqa.suse.de/tests/13964002#step/logs_from_installation_system/28.

Actions #9

Updated by hjluo 30 days ago

Actions #10

Updated by pcervinka 30 days ago

Yes, I confirm the same. There are no installer issues in HPC installation jobs.

Actions #11

Updated by JERiveraMoya 24 days ago

  • Status changed from New to Rejected
Actions

Also available in: Atom PDF