On Sun, Dec 01, 2013 at 04:00:01AM +0200, Stefano Rivera wrote:
> Hi Hector (2013.12.01_03:56:26_+0200)
> > 2013/11/30 Stefano Rivera <[email protected]>:
> > > PyPy usually builds on i386 (without any trouble) and armel (fairly
> > > slowly). The lastest upload timed out on both. We should retry (and
> > > possibly raise the timeouts a bit).
> > >
> > >   gb pypy_2.2.1+dfsg-1 . i386 armel
> > 
> > On armel:
> > E: Caught signal 'Terminated': terminating immediately
> > Build killed with signal TERM after 600 minutes of inactivity
> > 
> > It is already increased.
> 
> And re-looking at the i386 timeout, it's something I've seen before -
> probably failing to clean up a subprocess, and never temininating.
> Unfortunately I've never figured that one out, it happens occasionally.
> Increasing the i386 timeout wouldn't help.

I gave it back, we'll see what happens.


Kurt


-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
Archive: http://lists.debian.org/[email protected]

Reply via email to