View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0015906 | Buildsys | community buildsys | public | 2019-03-10 16:39 | 2019-03-16 11:32 |
Reporter | gfidente | Assigned To | |||
Priority | high | Severity | major | Reproducibility | always |
Status | resolved | Resolution | fixed | ||
Summary | 0015906: ppc64le builds for ceph/nautilus killed by OOM | ||||
Description | Hi, builds of Ceph up to the Luminous version used to work for all three supported archs (x86_64, ppc64le and aarm64), but builds of the Nautilus version appear to fail when killed with the ppc64le going OOM [1]. This is seen even when using -j1. How much memory can be consumed by the ppc64le workers? Would it be possible to increase the amount of memory available? 1. https://cbs.centos.org/koji/buildinfo?buildID=25271 | ||||
Additional Information | x86_64 builds complete successfully | ||||
Tags | No tags attached. | ||||
Hi, I've balanded resources between some nodes and I bumped available memory/vcpus for the ppc64le builders in CBS. Can you kick another build and see if that works now ? It should |
|
I see that kicked rebuild is still ongoing (at least on aarch64) but on that build it's only one using one core .. so are you still using -j1 ? maybe time to optimize this and use all available cores on all builders ? https://cbs.centos.org/koji/taskinfo?taskID=742749 |
|
hi, thanks for helping I can see the ppc4le build passed now though ... I did purposely use -j1 to consume the least amount possible of memory, I can try optimzing yes; will launch a new build as soon as this one finishes |
|
Date Modified | Username | Field | Change |
---|---|---|---|
2019-03-10 16:39 | gfidente | New Issue | |
2019-03-14 15:11 | arrfab | Status | new => feedback |
2019-03-14 15:11 | arrfab | Note Added: 0033999 | |
2019-03-15 08:19 | arrfab | Note Added: 0034006 | |
2019-03-15 08:23 | gfidente | Note Added: 0034007 | |
2019-03-15 08:23 | gfidente | Status | feedback => assigned |
2019-03-16 11:32 | arrfab | Status | assigned => resolved |
2019-03-16 11:32 | arrfab | Resolution | open => fixed |