On Mon 30 Jan 2023 04:13:39 PM CST, Simon Vogl wrote: >Thanks for the analysis, that could theoretically also be the case. > >What confuses me is that the compilation works fine on i586. If the >problem you describe would be the cause, shouldn't the OOM occur >equally on both i586 and x86_64? Or am I missing something here? > >The vm's total memory usage seems to be below 1GB when OOM happens >according to this line: > >[ T339] Out of memory: Killed process 4105 >(cc1plus)total-vm:891536kB,anon-rss:368340kB,file-rss:0kB,shmem-rss:0kB,UID:399 > pgtables:1756kB oom_score_adj:0 > >so maybe giving the workers a bit more than 1GB memory is still worth >trying as a work-around? > <snip> Hi Checking buildwk1:1 through 4 and buildwk3:1 through 4 with `osc workerinfo x86_64:buildwk1:1` shows the workers are using jobs=1, memory=512M and swap=512.
-- Cheers Malcolm °¿° (Linux Counter #276890) Tumbleweed 20230129 | GNOME Shell 43.2 | 6.1.8-1-default HP Z440 | Xeon E5-2690 V3 X24 @ 2.60GHz | Nvidia Quadro T400/Tesla P4 up 14:58, 2 users, load average: 0.45, 0.68, 0.52 _______________________________________________ Packman mailing list [email protected] https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
