On Tue, Aug 31, 2021 at 11:17:18AM +0200, Dan Horák wrote:
On Tue, 31 Aug 2021 11:13:40 +0200 Dan Horák dan@danny.cz wrote:
On Tue, 31 Aug 2021 10:07:38 +0100 "Richard W.M. Jones" rjones@redhat.com wrote:
https://koji.fedoraproject.org/koji/taskinfo?taskID=74840901
How should I interpret this?
something is killing the build in progress (like oomd?) and inspection of the builders (looks at least x86_64 + ppc64le + s390x are affected) in question is needed ...
from buildvm-s390x-22.s390.fedoraproject.org
[290483.759667] oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=/,mems_allowed=0,global_oom,task_memcg=/system.slice/kojid.service,task=dnf,pid=1739780,uid=0 [290483.759690] Out of memory: Killed process 1739780 (dnf) total-vm:16787488kB, anon-rss:14531544kB, file-rss:4kB, shmem-rss:0kB, UID:0 pgtables:32650kB oom_score_adj:0 [290486.777808] oom_reaper: reaped process 1739780 (dnf), now anon-rss:0kB, file-rss:0kB, shmem-rss:0kB
killed dnf, that's not good ...
Here's another one, different package, different arch, but same sort of error:
https://koji.fedoraproject.org/koji/taskinfo?taskID=74848368
It's tricky to understand from the log or the OOM report if there's a particular package that dnf is trying to install that is causing the problem, and which package that could be.
However I see there are other recent f36 builds that have not failed (including glibc) so it cannot be a completely generic dnf problem:
https://koji.fedoraproject.org/koji/builds?tagID=44414
Rich.