On 05/09/26 at 14:53 +0530, Nilesh Patra wrote: > Hi Ben, Bastien, Lucas, > > > Quoting Ben Hutchings: > > I tried running lintian on a full amd64 build of linux. lintian > > allocated about 23 GiB of VM and then was OOM-killed before generating > > any output. > > There have been several releases since this bug report was filed (almost 5 > years > back(!)) and there have been many memory and performance based fixes so far. > I don't have the compute to build/run checks on linux myself. Would you > be able to confirm if the memory usage is in sensible limits now with the > latest > release 2.140.0 please? > > > I notice that <https://lintian.debian.org/sources/linux> has no > > information, probably because of this. > > > > This is a regression in lintian, but I don't know how long ago it > > happened. > > I can see linux has lintian tags in the UDD (lintian.d.o was revamped and does > not show package-specific tags now - UDD does that job): > > https://udd.debian.org/lintian/?packages=linux > > Lucas, will you be able to comment on how much memory linux uses on UDD > workers?
Hi, I recently improved the UDD lintian orchestrator so that it now stores CPU time and peak memory usage. I am currently re-processing all packages with 2.139.0 to collect that data, and then I will upgrade to 2.140.0 and compare results. The whole process will take a few days. But linux/7.2.3-1~exp1 was already reprocessed, and uses at most 27.7 GB (for the linux-image-7.2-loong64-dbg binary). That's with 2.139.0. The following UDD query is useful: select source, version, package, package_version, architecture, memory_peak_bytes / 1024/1024/1024 as memory_peak_gb from lintian_logs where memory_peak_bytes is not null order by 6 desc; Lucas
