Your message dated Sat, 23 Mar 2019 16:08:07 +0100
with message-id <[email protected]>
and subject line closing remaining openjdk-6 bugs
has caused the Debian Bug report #519012,
regarding openjdk-6: Requests upto 18 GB of RAM during build.
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.)
--
519012: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=519012
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: openjdk-6
Version: 6b14-1.5~pre1-3
Hi,
On the buildd I have vm.overcommit_memory set to 2, so restricting
the amount of RAM applications can requested to what is available
of RAM and swap. The buildd has 2 GB of RAM and 20 GB of swap.
During the build of openjdk-6, the box had 10 GB commited for most
of the time, with a peak of 19 GB near the end. But at no time
anything was really using that much RAM. Active only showed a
peak of 1 GB, and the amount of cache was always 1 GB or more.
So it seems this currently wasn't a problem. But future builds
might fail instead because memory allocation fails. It would
be a good thing if you didn't allocate so much RAM you're never
going to use.
Kurt
--- End Message ---
--- Begin Message ---
Version: 6b41-1.13.13-1+rm
Hi,
openjdk-6 was last released with Debian 7.0 (wheezy), which had its LTS
support end nearly a year ago and which has now been archived.
I'm therefore closing the remaining openjdk-6 bugs, assuming they are no
longer relevant for newer (and still supported) openjdk releases.
Andreas
--- End Message ---
