action #59244
closed[functional][y][timeboxed:3h] test fails in first_boot - Gnome-shell oom-killed
0%
Description
Observation¶
So we need to file a bug for this.
We have this right after logging in:
Nov 08 05:26:24 install kernel: Free swap = 0kB
[...]
Nov 08 05:26:24 install kernel: oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=/,mems_allowed=0,global_oom,task_memcg=/,task=gnome-shell,pid=3577,uid=471
Nov 08 05:26:24 install kernel: Out of memory: Killed process 3577 (gnome-shell) total-vm:2480640kB, anon-rss:56512kB, file-rss:0kB, shmem-rss:3136kB
Nov 08 05:26:24 install kernel: oom_reaper: reaped process 3577 (gnome-shell), now anon-rss:0kB, file-rss:0kB, shmem-rss:3200kB
It may be a product bug, but maybe the test would just pass if we had more swap, we have only 300MB which goes against the usual recommendations to have at least swap=ram. The test module passes when we have more swap, as in btrfs test. I'd rather give it a try before reporting this as a bug.
openQA test in scenario sle-15-SP2-Online-ppc64le-RAID0@ppc64le-no-tmpfs fails in
first_boot
Test suite description¶
Maintainer: slindomansilla, jrauch
Installation of RAID0 using expert partitioner
Reproducible¶
Fails since (at least) Build 72.1
Expected result¶
Last good: (unknown) (or more recent)
Further details¶
Always latest result in this scenario: latest
Updated by riafarov over 4 years ago
- Due date set to 2019-12-03
- Target version set to Milestone 29
I strongly believe that this is a bug. Our RAM requirements hasn't changed for the distribution, so we need to report this as a bug.
Updated by riafarov over 4 years ago
- Subject changed from [functional][y]test fails in first_boot - Gnome-shell oom-killed to [functional][y][timeboxed:3h] test fails in first_boot - Gnome-shell oom-killed
- Description updated (diff)
- Status changed from New to Workable
Updated by riafarov over 4 years ago
- Due date deleted (
2019-12-03) - Status changed from Workable to Resolved
- Assignee set to riafarov