Your message dated Sun, 4 Dec 2022 13:21:34 +0100
with message-id <[email protected]>
and subject line Re: spades: Fails to build with unhelpful error message in a
"low" memory machine
has caused the Debian Bug report #853113,
regarding spades: Fails to build with unhelpful error message in a "low" memory
machine
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
853113: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853113
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:spades
Version: 3.9.1+dfsg-1
Dear maintainer:
I can't build this package on a machine with 2 GB RAM and 2 GB swap.
This is usually not a problem by itself, because each package needs
what it needs, and therefore this bug is not severity serious as FTBFS
bugs usually are, but it is a problem in this package because of two
reasons:
* Looking at Committed_AS in /proc/meminfo during the build, the
package does not seem to need more than 2GB of RAM in either case.
* There is not a clear message saying "Memory exhausted" or
"not enough memory" or anything like that.
I attach two different build logs. The one called "ok" was made
on a machine with 6GB of RAM and 4 GB of swap. The one called "notok"
was made on a machine with 2 GB of RAM and 2 GB of swap.
Please take a look at the second build log and try to determine how
anybody is supposed to know that there was not enough memory from the
build log.
(Well, maybe the package is actually doing something weird with the
memory and maybe it should work after all).
To reproduce please try to build this on a single-CPU machine having
2 GB of RAM and 2 GM of swap.
[ Note: In the subject of this bug I've used "low" memory between quotes
because 2 GB of RAM is not actually so small. Among the 17209 source
packages that may be built with "dpkg-buildpackage -A", 17089 of them,
that is, 99.3% of them, need less than 2 GB of RAM to build ].
Thanks.
spades_3.9.1+dfsg-1_amd64-20170129T004745Z.ok.gz
Description: application/gzip
spades_3.9.1+dfsg-1_amd64-20170129T004422Z.notok.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Version: 3.13.1+dfsg-2
El 4/12/22 a las 10:22, Andreas Tille escribió:
I admit we did not put any effort on this bug report. Since this bug is
now five years old and there are several upstreams versions released I
wonder whether this problem persists or whether we can close this bug
report.
Thanks for asking.
I'm marking this as fixed myself after a quick test I did in stable
using a self-hosted KVM machine with 2GB RAM and 2 GB swap. This is how
it failed:
<jemalloc>: Error in calloc(): out of memory
== Error == system call for:
"['/<<PKGBUILDDIR>>/install_spades/bin/spades-hammer',
'/<<PKGBUILDDIR>>/spades_test/corr
ected/configs/config.info']" finished abnormally, err code: -6
Previously, only the "err code: -6" line was shown, not the "out of
memory" message, so this seems to be fixed now.
Thanks a lot.
--- End Message ---
