On Fri, 26 Jul 2019 09:02:57 +0200 Dan Čermák dan.cermak@cgc-instruments.com wrote:
Jason L Tibbitts III tibbs@math.uh.edu writes:
> "KK" == Kaleb Keithley kkeithle@redhat.com writes:
KK> I built the latest ceph-14 (14.2.2) on rawhide successfully two KK> days ago. Two different builds on f30 built or are building KK> fine on x86_64, i686, and aarch64, but failed with different KK> errors on ppc64le at different places in the build. One looks KK> like it ran out of space in the file system. The other may have KK> been OOM killed (?).
There was just a bit of talk about this in IRC. The issue seems to be that the CPU count of the PPC64le builders was bumped from 4 to 12, but the amount of memory was unchanged at 10GB RAM/2GB swap. This could potentially cause resource exhaustion.
Seems they've now been bumped to 22GB of RAM, which should help with OOM issues but probably not with disk space issues.
Although not directly related, but I thought I'll throw this in: openSUSE has a handy package called memory-constraints which features a single macro: %limit_build.
You give this macro the amount of RAM you expect make/ninja/$my_build_cmd to consume at peak per thread and it sets the number of jobs via overriding _smp_mflags so that you won't OOM.
Source: https://build.opensuse.org/package/view_file/network:chromium/memory-constra...
That could be useful for arches which have builders with a lot of cores but not a lot of RAM or builds which consume excessive amounts.
long time ago I filed a bug/RFE to compute the "-j" value from the number of cpus and available memory, still waiting on me to actually implement it ;-)
Dan