[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: [libgadu] Build killed with signal TERM after <N> minutes of inactivity



On Sat, Jun 23, 2012 at 09:43:20AM -0300, Samuel Thibault wrote:
> Marcin Owsiany, le Sat 23 Jun 2012 10:53:45 +0100, a écrit :
> > Can someone explain what this message actually means? How is
> > "inactivity" determined? Is the build really idling, or just taking that
> > long?
> 
> It means the build didn't produce any output during that time.

Output to disk or to stdout?

> > The build times on other architectures were 2-5 minutes (10-13 on arm*).
> > 
> > Is there a way to bump this threshold, to see if giving it more time
> > helps?
> 
> Well, I don't think it will help.  3 hours is already very long,
> compared to even arm figures.  It most probably just hangs.  You could
> give it a try on the exodar.debian.net porter machine.

I will.

-- 
Marcin Owsiany <porridge@debian.org>             http://marcin.owsiany.pl/
GnuPG: 2048R/02F946FC  35E9 1344 9F77 5F43 13DD  6423 DBF4 80C6 02F9 46FC


Reply to: