On 15/03/10 at 10:23 +0900, Changwoo Ryu wrote:
> On Mon, Mar 15, 2010 at 5:10 AM, Lucas Nussbaum
> <lu...@lucas-nussbaum.net> wrote:
> > On 14/03/10 at 17:05 +0900, Changwoo Ryu wrote:
> >> Building this package doesn't always fail. It depends on your build
> >> machine's memory and CPU.
> >
> > That build machine has 8 cores and 32 GB of RAM.
> 
> Please check ulimit values. One of them may limit memory max per process.
> 
> >> Well actually I'm also the upstream author..  :)  Building this package
> >> requires insanely HUGE memory and it takes a long time. It's mainly
> >> because it uses a poor algorithm to build combinated words.
> >
> > It built fine for me a few days ago in less than 5 minutes.
> > Is it possible that it fails randomly?
> 
> I don't think so.
> 
> There must be something different on the build environment. Low memory
> situation is what I can only imagine from the build log ("terminated
> by signal").

That's sbuild killing the build after 60 minutes without output.
-- 
| Lucas Nussbaum
| lu...@lucas-nussbaum.net   http://www.lucas-nussbaum.net/ |
| jabber: lu...@nussbaum.fr             GPG: 1024D/023B3F4F |



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to