| Summary: | OOM while building chromium-browser-privacy-85.0.4183.102-1 | ||
|---|---|---|---|
| Product: | Infrastructure | Reporter: | qvint <dotqvint> |
| Component: | Build System | Assignee: | Nicolas Chauvet <kwizart> |
| Status: | RESOLVED FIXED | ||
| Severity: | major | CC: | leigh123linux, lxtnow |
| Priority: | P1 | ||
| Version: | NA | ||
| Hardware: | x86_64 | ||
| OS: | GNU/Linux | ||
| namespace: | |||
|
Description
qvint
2020-09-16 10:31:22 CEST
Seems like all are related to buildvm-06 for some reason. It has the same amount of ram as buidlvm-05. What looks weird, is that at least the OOM occurs at compilation time not link time, so it shouldn't be the more RAM consuming steps... I've rebooted the vm, let's see if it's better. OK I've multiplied by 2 the CPU/RAM for theses builder. Please try to submit chromium tasks so each powerbuilder are loaded. Because the way koji handle builder ressources, best is to wait for the buildSRPMfromSCM task to end and a builder get assigned before to submit another build for a new branch. Thanks for your work on this. (In reply to qvint from comment #0) > The following build attempts have failed due to OOM at > buildvm-06.virt.rpmfusion.net: > > - http://koji.rpmfusion.org/koji/taskinfo?taskID=436976 > - http://koji.rpmfusion.org/koji/taskinfo?taskID=437261 > - http://koji.rpmfusion.org/koji/taskinfo?taskID=437277 > - http://koji.rpmfusion.org/koji/taskinfo?taskID=437298 > - http://koji.rpmfusion.org/koji/taskinfo?taskID=437306 Your builds on buildvm-07.virt.rpmfusion.net will be terminated at around 00:00UMT due to noise. Please run builds before 16:00UMT to ensure it has time to complete. There is an issue with obj/content/browser/browser/render_frame_host_impl.o I don't think it's memory related or there is a enormous memory leak there. This might have to be investigated on the gcc side eventually. @qvint. Can we close this issue ? We cannot have unlimited resources on builders, not even comparable to what google have to build chromium. So we will always be tight to memory constraint and regression that either gcc or chromium code base have. The absolute minimum is 16 GB of RAM, and as far as I can see, the builders have enough resources to build Chromium: - https://koji.rpmfusion.org/kojifiles/work/tasks/3798/443798/hw_info.log - https://koji.rpmfusion.org/kojifiles/work/tasks/3612/443612/hw_info.log Let me build Chromium 87, and if things go well, I'll close the issue. Build vm-07 is down currently due to maintenance, it should be up by 20/11/2020. Build succeeded, thank you. |