Re: Please retry failed pypy builds on i386 and armel

2013-12-03 Thread Kurt Roeckx
On Mon, Dec 02, 2013 at 08:25:33PM +0200, Stefano Rivera wrote: Hi Kurt (2013.12.01_14:44:20_+0200) I gave it back, we'll see what happens. Great, same failure on i386 :/ I tried locally (twice), and it built without issue. Retry again? I could also upload one of my builds, but I'd

Re: Please retry failed pypy builds on i386 and armel

2013-12-02 Thread Stefano Rivera
Hi Kurt (2013.12.01_14:44:20_+0200) I gave it back, we'll see what happens. Great, same failure on i386 :/ I tried locally (twice), and it built without issue. Retry again? I could also upload one of my builds, but I'd prefer it to build on a buildd. SR -- Stefano Rivera

Re: Please retry failed pypy builds on i386 and armel

2013-11-30 Thread Hector Oron
Hello, 2013/11/30 Stefano Rivera stefa...@debian.org: 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

Re: Please retry failed pypy builds on i386 and armel

2013-11-30 Thread Stefano Rivera
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi Hector (2013.12.01_03:56:26_+0200) 2013/11/30 Stefano Rivera stefa...@debian.org: 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