On Tue, Jan 4, 2022 at 3:03 PM Sam James <s...@gentoo.org> wrote: > > > > On 4 Jan 2022, at 22:58, Sam James <s...@gentoo.org> wrote: > > Crank down MAKEOPTS jobs if MAKEOPTS="-jN" is too high for the > amount of RAM available (uses amount declared as needed > in the ebuild). Typically should be ~2GB per job. > > Bug: https://bugs.gentoo.org/570534 > Signed-off-by: Sam James <s...@gentoo.org> > --- > eclass/check-reqs.eclass | 42 +++++++++++++++++++++++++++++++++++++--- > 1 file changed, 39 insertions(+), 3 deletions(-) > > > Note that we discussed this on GitHub a bit when I just posted it there > for some rough feedback: https://github.com/gentoo/gentoo/pull/23311. > > I think this is valuable for reducing invalid bug reports from OOM and > easing user experience. > > Still kind of a WIP/rough draft, but may be ready in this state. Need > more testing, so not planning on pushing yet or anything.
I'm still not sure I grasp why we cannot make OOMs easier to discover from portage. Most packages don't even use check-reqs, so your solution is very narrow (and I get why, because you get a lot of bug reports from the big packages that do use it.) Can we write a build log analyzer? -A PS: If this was a global change I'd downvote it. It's only for check-reqs though and most packages don't use check-reqs; I don't really care. I'd be concerned about adopting this kind of approach wider; its very much a bandaid.
