Bug#852106: [pkg-gnupg-maint] Bug#852106: gpgme1.0: Build allocates 200 GB as a normal thing

2017-01-23 Thread Santiago Vila
On Mon, Jan 23, 2017 at 05:41:29PM -0500, Daniel Kahn Gillmor wrote: > I'm open for suggestions for how to address this. We could just drop > THREAD_COUNT from 100 to 10 to reduce the RAM consumption, but that > would mean minimizing some of the concurrency that the test suite is > (rightly) tryi

Bug#852106: [pkg-gnupg-maint] Bug#852106: gpgme1.0: Build allocates 200 GB as a normal thing

2017-01-23 Thread Daniel Kahn Gillmor
Hi Santiago-- On Sat 2017-01-21 12:40:06 -0500, Santiago Vila wrote: > I have a cron job monitoring "Committed_AS" in /proc/meminfo every time > my autobuilders are running, that way I know how much memory each > package requires. > > Well, building gpgme1.0 allocates 100 GB, 200 GB and sometimes

Bug#852106: gpgme1.0: Build allocates 200 GB as a normal thing

2017-01-21 Thread Santiago Vila
Package: gpgme1.0 Version: 1.8.0-3 Hello dkg et al. I have a cron job monitoring "Committed_AS" in /proc/meminfo every time my autobuilders are running, that way I know how much memory each package requires. Well, building gpgme1.0 allocates 100 GB, 200 GB and sometimes 500 GB. To see how this